Methods and apparatus for using smart environment devices via application program interfaces

ABSTRACT

In one embodiment, one or more non-transitory, tangible, machine-readable media includes instructions to send one or more requests to retrieve, access, view, subscribe, or modify data in a data model representative of one or more smart environments. The data model includes a metadata object that includes an access token used to identify which user the data is associated with in the data model, a devices object that includes information related to one or more electronic devices, and a structures object that includes one or more references to the one or more electronic devices in the one or more smart environments.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a Non-Provisional application claiming priority toU.S. Provisional Patent Application No. 62/016,052, entitled “Methodsand Apparatus for Exploiting Application Programming Interfaces to SmartHome Environment Electronic Components”, filed Jun. 23, 2014, which isherein incorporated by reference. This application incorporates in theirentirety co-pending U.S. patent application Ser. No. 14/722,003(NEST:0051A), Ser. No. 14/722,012 (NEST:0051B), Ser. No. 14/722,023(NEST:0051C), Ser. No. 14/722,026 (NEST:0051D), Ser. No. 14/722,032(NEST:0051E), entitled “METHODS AND APPARATUS FOR USING SMARTENVIRONMENT DEVICES VIA APPLICATION PROGRAM INTERFACES”, filed May 26,2015.

BACKGROUND

This disclosure relates to accessing data and/or controlling electronicdevices (e.g., smart devices) via one or more application programminginterfaces (APIs).

This section is intended to introduce the reader to various aspects ofart that may be related to various aspects of the present disclosure,which are described and/or claimed below. This discussion is believed tobe helpful in providing the reader with background information tofacilitate a better understanding of the various aspects of the presentdisclosure. Accordingly, it should be understood that these statementsare to be read in this light, and not as admissions of prior art.

People interact with a number of different electronic devices on a dailybasis. In a home setting, for example, a person may interact with smartthermostats, lighting systems, alarm systems, entertainment systems, anda variety of other electronic devices. To interact with some of theseelectronic devices, a person may communicate a command using anapplication program running on another electronic device. For instance,a person may control the temperature setting on a smart thermostat usingan application program running on a smartphone. The application programmay communicate with a secure online service that interacts with thatthermostat.

To preserve the user experience associated with an electronic device,the manufacturer of the electronic device may develop the applicationprograms to control the electronic device. Opening access to theelectronic devices to third party developers, however, may potentiallyimprove the experience of some people with the devices—but only if thirdparty application programs do not cause the electronic devices to behavein an undesirable manner. Accordingly, while it may be desirable to openaccess to the electronic devices to third party developers, it may alsobe desirable to place restrictions on that access so as to reduce therisk that the third party access may negatively impact the operation ofthe electronic devices and thus the user experience associated withthose devices.

SUMMARY

A summary of certain embodiments disclosed herein is set forth below. Itshould be understood that these aspects are presented merely to providethe reader with a brief summary of these certain embodiments and thatthese aspects are not intended to limit the scope of this disclosure.Indeed, this disclosure may encompass a variety of aspects that may notbe set forth below.

According to embodiments of this disclosure, applications may accessdifferent installations of smart home devices (e.g., via an applicationprogramming interface (API)). Namely, the third party applications maycommunicate not directly with a smart home device, but rather through adevice service. The device service may provide a corresponding updatesignal to the target smart home device based on one or more factors suchas operation status parameters of the device.

Various refinements of the features noted above may exist in relation tovarious aspects of the present disclosure. Further features may also beincorporated in these various aspects as well. These refinements andadditional features may exist individually or in any combination. Forinstance, various features discussed below in relation to one or more ofthe illustrated embodiments may be incorporated into any of theabove-described aspects of the present disclosure alone or in anycombination. The brief summary presented above is intended only tofamiliarize the reader with certain aspects and contexts of embodimentsof the present disclosure without limitation to the claimed subjectmatter.

BRIEF DESCRIPTION OF THE DRAWINGS

Various aspects of this disclosure may be better understood upon readingthe following detailed description and upon reference to the drawings inwhich:

FIG. 1 is a block diagram of a smart home device, in accordance with anembodiment;

FIG. 2 is a block diagram of a connected smart home environment thatincludes a number of smart home devices, in accordance with anembodiment;

FIG. 3 is a block diagram illustrating a manner of controlling and/oraccessing the smart home environment using services over the internet,in accordance with an embodiment;

FIG. 4 is a block diagram of processing paradigms that may be used tocontrol devices of the smart home environment, in accordance with anembodiment;

FIG. 5 is a block diagram of a system that provides access to smart homedevices, in accordance with an embodiment;

FIG. 6 is a block diagram of a system 180 that uses an API 90 to accessone or more device services 84 to request data from, control, and/orstore data that may be useful to the smart devices, in accordance withan embodiment;

FIG. 7 illustrates a process for providing data requests via thesubscription-based device service, in accordance with an embodiment;

FIG. 8 illustrates a process for providing data from smart devicesand/or structures to a client, in accordance with an embodiment;

FIG. 9 illustrates a flow diagram of a process for a user to authorize aclient to access user data in the data model via the device service, inaccordance with an embodiment;

FIG. 10 illustrates the resource access permission page of FIG. 9, inaccordance with an embodiment;

FIG. 11 illustrates a block diagram of a system for authorizing clientsto use a user's smart device data via the web, in accordance with anembodiment;

FIG. 12 illustrates a sequence diagram for authorizing clients to use auser's smart device data using the system of FIG. 11 via the web, inaccordance with an embodiment;

FIG. 13 illustrates a block diagram of a system for authorizing clientsto use a user's smart device data via a PIN when the devices do not havea web UI, in accordance with an embodiment;

FIG. 14 illustrates a sequence diagram for authorizing clients to use auser's smart device data using the system of FIG. 13 via the PIN, inaccordance with an embodiment;

FIG. 15 is a schematic diagram, illustrating a system third-party vendorand device provisioning that enables consumption of third-party devicedata via the API, in accordance with an embodiment;

FIG. 16 is a flowchart, illustrating a process for provisioningthird-party vendors and third-party devices, such that third-partydevice data may be consumed via the API, in accordance with anembodiment; and

FIG. 17 is a relational diagram, illustrating a relationship of entitiesstored in the system when provisioning third-parties/third-party devicesin the system, in accordance with an embodiment.

DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS

One or more specific embodiments will be described below. In an effortto provide a concise description of these embodiments, not all featuresof an actual implementation are described in the specification. Itshould be appreciated that in the development of any such actualimplementation, as in any engineering or design project, numerousimplementation-specific decisions may be made to achieve the developers'specific goals, such as compliance with system-related andbusiness-related constraints, which may vary from one implementation toanother. Moreover, it should be appreciated that such a developmenteffort might be complex and time consuming, but would nevertheless be aroutine undertaking of design, fabrication, and manufacture for those ofordinary skill having the benefit of this disclosure.

Embodiments of the present disclosure relate to an electronic device,such as a thermostat or a hazard detector (e.g., smoke detector, carbonmonoxide detector, etc.), that may be disposed in a building (e.g., homeor office) such that the electronic device may detect the presence of ahuman being in the building and distinguish between the presence of thehuman being and a pet. Generally, the electronic device may employ asensor, such as a passive infrared (PIR) sensor, to detect the presenceof a human being. However, each PIR sensor may be inherently sensitiveto different levels of noise. By accounting for the differentsensitivity levels of each PIR sensor, the electronic device may improveits detection of human beings and better distinguish between thepresence of human beings and pets.

Keeping this in mind, the electronic device may include a low-powerprocessor that may store the sensor measurements acquired by the PIRsensor during a time period when the electronic device does not expect ahuman in the building or portion of the building being monitored byelectronic device is not expected to have a human being present. In oneembodiment, after storing the sensor measurements over some period oftime, the low-power processor may send the stored sensor measurements toa high-power processor of the electronic device. The high-powerprocessor may then calculate a threshold or adjust the previousthreshold for determining a presence of a human based on the storedsensor measurements that correspond to the time period when a humanbeing is likely not present in the building. The high-power processormay then send the newly calculated or the adjusted threshold to thelow-power processor. The low-power processor may then use the newlycalculated or the adjusted threshold to detect the presence of a human.Since the new threshold is calculated based on the respective sensormeasurements for the respective PIR sensor of a respective electronicdevice, the new threshold may compensate for the inherent sensitivitycharacteristics of the respective PIR sensor. As a result, theelectronic device may detect the presence of a human being moreeffectively and efficiently.

Smart Device in Smart Home Environment

By way of introduction, FIG. 1 illustrates an example of a generaldevice 10 that may that may be disposed within a building environment.In one embodiment, the device 10 may include one or more sensors 12, auser-interface component 14, a power supply 16 (e.g., including a powerconnection and/or battery), a network interface 18, a high-powerprocessor 20, a low-power processor 22, a passive infrared (PIR) sensor24, a light source 26, and the like.

The sensors 12, in certain embodiments, may detect various propertiessuch as acceleration, temperature, humidity, water, supplied power,proximity, external motion, device motion, sound signals, ultrasoundsignals, light signals, fire, smoke, carbon monoxide,global-positioning-satellite (GPS) signals, radio-frequency (RF), otherelectromagnetic signals or fields, or the like. As such, the sensors 12may include temperature sensor(s), humidity sensor(s), hazard-relatedsensor(s) or other environmental sensor(s), accelerometer(s),microphone(s), optical sensors up to and including camera(s) (e.g.,charged coupled-device or video cameras), active or passive radiationsensors, GPS receiver(s) or radiofrequency identification detector(s).While FIG. 1 illustrates an embodiment with a single sensor, manyembodiments may include multiple sensors. In some instances, the device10 may include one or more primary sensors and one or more secondarysensors. Here, the primary sensor(s) may sense data central to the coreoperation of the device (e.g., sensing a temperature in a thermostat orsensing smoke in a smoke detector), while the secondary sensor(s) maysense other types of data (e.g., motion, light or sound), which can beused for energy-efficiency objectives or smart-operation objectives.

One or more user-interface components 14 in the device 10 may receiveinput from the user and/or present information to the user. The receivedinput may be used to determine a setting. In certain embodiments, theuser-interface components may include a mechanical or virtual componentthat responds to the user's motion. For example, the user canmechanically move a sliding component (e.g., along a vertical orhorizontal track) or rotate a rotatable ring (e.g., along a circulartrack), or the user's motion along a touchpad may be detected. Suchmotions may correspond to a setting adjustment, which can be determinedbased on an absolute position of a user-interface component 14 or basedon a displacement of a user-interface components 14 (e.g., adjusting aset point temperature by 1 degree F. for every 10° rotation of arotatable-ring component). Physically and virtually movableuser-interface components can allow a user to set a setting along aportion of an apparent continuum. Thus, the user may not be confined tochoose between two discrete options (e.g., as would be the case if upand down buttons were used) but can quickly and intuitively define asetting along a range of possible setting values. For example, amagnitude of a movement of a user-interface component may be associatedwith a magnitude of a setting adjustment, such that a user maydramatically alter a setting with a large movement or finely tune asetting with a small movement.

The user-interface components 14 may also include one or more buttons(e.g., up and down buttons), a keypad, a number pad, a switch, amicrophone, and/or a camera (e.g., to detect gestures). In oneembodiment, the user-interface component 14 may include aclick-and-rotate annular ring component that may enable the user tointeract with the component by rotating the ring (e.g., to adjust asetting) and/or by clicking the ring inwards (e.g., to select anadjusted setting or to select an option). In another embodiment, theuser-interface component 14 may include a camera that may detectgestures (e.g., to indicate that a power or alarm state of a device isto be changed). In some instances, the device 10 may have one primaryinput component, which may be used to set a plurality of types ofsettings. The user-interface components 14 may also be configured topresent information to a user via, e.g., a visual display (e.g., athin-film-transistor display or organic light-emitting-diode display)and/or an audio speaker.

The power-supply component 16 may include a power connection and/or alocal battery. For example, the power connection may connect the device10 to a power source such as a line voltage source. In some instances,an AC power source can be used to repeatedly charge a (e.g.,rechargeable) local battery, such that the battery may be used later tosupply power to the device 10 when the AC power source is not available.

The network interface 18 may include a component that enables the device10 to communicate between devices. As such, the network interface 18 mayenable the device 10 to communicate with other devices 10 via a wired orwireless network. The network interface 18 may include a wireless cardor some other transceiver connection to facilitate this communication.

The high-power processor 20 and the low-power processor 22 may supportone or more of a variety of different device functionalities. As such,the high-power processor 20 and the low-power processor 22 may eachinclude one or more processors configured and programmed to carry outand/or cause to be carried out one or more of the functionalitiesdescribed herein. In one embodiment, the high-power processor 20 and thelow-power processor 22 may include general-purpose processors carryingout computer code stored in local memory (e.g., flash memory, harddrive, and/or random access memory), special-purpose processors orapplication-specific integrated circuits, combinations thereof, and/orusing other types of hardware/firmware/software processing platforms. Incertain embodiments, the high-power processor 20 may executecomputationally intensive operations such as operating theuser-interface component 14 and the like. The low-power processor 22, onthe other hand, may manage less complex processes such as detecting ahazard or temperature from the sensor 12. In one embodiment, thelow-power processor may wake or initialize the high-power processor forcomputationally intensive processes.

By way of example, the high-power processor 20 and the low-powerprocessor 22 may detect when a location (e.g., a house or room) isoccupied (i.e., includes a presence of a human), up to and includingwhether it is occupied by a specific person or is occupied by a specificnumber of people (e.g., relative to one or more thresholds). In oneembodiment, this detection can occur, e.g., by analyzing microphonesignals, detecting user movements (e.g., in front of a device),detecting openings and closings of doors or garage doors, detectingwireless signals, detecting an internet protocol (IP) address of areceived signal, detecting operation of one or more devices within atime window, or the like. Moreover, the high-power processor 20 and thelow-power processor 22 may include image recognition technology toidentify particular occupants or objects.

In certain embodiments, the high-power processor 20 and the low-powerprocessor 22 may detect the presence of a human using the PIR sensor 24.The PIR sensor 24 may be a passive infrared sensor that may measuresinfrared (IR) light radiating from objects in its field of view. Assuch, the PIR sensor 24 may detect the Infrared radiation emitted froman object.

In some instances, the high-power processor 20 may predict desirablesettings and/or implement those settings. For example, based on thepresence detection, the high-power processor 20 may adjust devicesettings to, e.g., conserve power when nobody is home or in a particularroom or to accord with user preferences (e.g., general at-homepreferences or user-specific preferences). As another example, based onthe detection of a particular person, animal or object (e.g., a child,pet or lost object), the high-power processor 20 may initiate an audioor visual indicator of where the person, animal or object is or mayinitiate an alarm or security feature if an unrecognized person isdetected under certain conditions (e.g., at night or when lights areoff).

In some instances, devices may interact with each other such that eventsdetected by a first device influence actions of a second device. Forexample, a first device can detect that a user has entered into a garage(e.g., by detecting motion in the garage, detecting a change in light inthe garage or detecting opening of the garage door). The first devicecan transmit this information to a second device via the networkinterface 18, such that the second device can, e.g., adjust a hometemperature setting, a light setting, a music setting, and/or asecurity-alarm setting. As another example, a first device can detect auser approaching a front door (e.g., by detecting motion or sudden lightpattern changes). The first device may, e.g., cause a general audio orvisual signal to be presented (e.g., such as sounding of a doorbell) orcause a location-specific audio or visual signal to be presented (e.g.,to announce the visitor's presence within a room that a user isoccupying).

In addition to detecting various types of events, the device 10 mayinclude a light source 26 that may illuminate when a living being, suchas a human, is detected as approaching. The light source 26 may includeany type of light source such as one or more light-emitting diodes orthe like. The light source 26 may be communicatively coupled to thehigh-power processor 20 and the low-power processor 22, which mayprovide a signal to cause the light source 26 to illuminate.

Keeping the foregoing in mind, FIG. 2 illustrates an example of asmart-home environment 30 within which one or more of the devices 10 ofFIG. 1, methods, systems, services, and/or computer program productsdescribed further herein can be applicable. The depicted smart-homeenvironment 30 includes a structure 32, which can include, e.g., ahouse, office building, garage, or mobile home. It will be appreciatedthat devices can also be integrated into a smart-home environment 30that does not include an entire structure 32, such as an apartment,condominium, or office space. Further, the smart home environment cancontrol and/or be coupled to devices outside of the actual structure 32.Indeed, several devices in the smart home environment need notphysically be within the structure 32 at all. For example, a devicecontrolling a pool heater or irrigation system can be located outside ofthe structure 32.

The depicted structure 32 includes a plurality of rooms 38, separated atleast partly from each other via walls 40. The walls 40 can includeinterior walls or exterior walls. Each room can further include a floor42 and a ceiling 44. Devices can be mounted on, integrated with and/orsupported by a wall 40, floor 42 or ceiling 44.

In some embodiments, the smart-home environment 30 of FIG. 2 includes aplurality of devices 10, including intelligent, multi-sensing,network-connected devices, that can integrate seamlessly with each otherand/or with a central server or a cloud-computing system to provide anyof a variety of useful smart-home objectives. The smart-home environment30 may include one or more intelligent, multi-sensing, network-connectedthermostats 46 (hereinafter referred to as “smart thermostats 46”), oneor more intelligent, network-connected, multi-sensing hazard detectionunits 50 (hereinafter referred to as “smart hazard detectors 50”), andone or more intelligent, multi-sensing, network-connected entrywayinterface devices 52 (hereinafter referred to as “smart doorbells 52”).According to embodiments, the smart thermostat 46 may include a Nest®Learning Thermostat—1st Generation T100577 or Nest® LearningThermostat—2nd Generation T200577 by Nest Labs, Inc., among others. Thesmart thermostat 46 detects ambient climate characteristics (e.g.,temperature and/or humidity) and controls a HVAC system 48 accordingly.

The smart hazard detector 50 may detect the presence of a hazardoussubstance or a substance indicative of a hazardous substance (e.g.,smoke, fire, or carbon monoxide). The smart hazard detector 50 mayinclude a Nest® Protect that may include sensors 12 such as smokesensors, carbon monoxide sensors, and the like. As such, the hazarddetector 50 may determine when smoke, fire, or carbon monoxide may bepresent within the building.

The smart doorbell 52 may detect a person's approach to or departurefrom a location (e.g., an outer door), control doorbell functionality,announce a person's approach or departure via audio or visual means, orcontrol settings on a security system (e.g., to activate or deactivatethe security system when occupants go and come). The smart doorbell 52may interact with other devices 10 based on whether someone hasapproached or entered the smart-home environment 30.

In some embodiments, the smart-home environment 30 further includes oneor more intelligent, multi-sensing, network-connected wall switches 54(hereinafter referred to as “smart wall switches 54”), along with one ormore intelligent, multi-sensing, network-connected wall plug interfaces56 (hereinafter referred to as “smart wall plugs 56”). The smart wallswitches 54 may detect ambient lighting conditions, detectroom-occupancy states, and control a power and/or dim state of one ormore lights. In some instances, smart wall switches 54 may also controla power state or speed of a fan, such as a ceiling fan. The smart wallplugs 56 may detect occupancy of a room or enclosure and control supplyof power to one or more wall plugs (e.g., such that power is notsupplied to the plug if nobody is at home).

Still further, in some embodiments, the device 10 within the smart-homeenvironment 30 may further includes a plurality of intelligent,multi-sensing, network-connected appliances 58 (hereinafter referred toas “smart appliances 58”), such as refrigerators, stoves and/or ovens,televisions, washers, dryers, lights, stereos, intercom systems,garage-door openers, floor fans, ceiling fans, wall air conditioners,pool heaters, irrigation systems, security systems, and so forth.According to embodiments, the network-connected appliances 58 are madecompatible with the smart-home environment by cooperating with therespective manufacturers of the appliances. For example, the appliancescan be space heaters, window AC units, motorized duct vents, etc. Whenplugged in, an appliance can announce itself to the smart-home network,such as by indicating what type of appliance it is, and it canautomatically integrate with the controls of the smart-home. Suchcommunication by the appliance to the smart home can be facilitated byany wired or wireless communication protocols known by those havingordinary skill in the art. The smart home also can include a variety ofnon-communicating legacy appliances 68, such as old conventionalwasher/dryers, refrigerators, and the like which can be controlled,albeit coarsely (ON/OFF), by virtue of the smart wall plugs 56. Thesmart-home environment 30 can further include a variety of partiallycommunicating legacy appliances 70, such as infrared (“IR”) controlledwall air conditioners or other IR-controlled devices, which can becontrolled by IR signals provided by the smart hazard detectors 50 orthe smart wall switches 54.

According to embodiments, the smart thermostats 46, the smart hazarddetectors 50, the smart doorbells 52, the smart wall switches 54, thesmart wall plugs 56, and other devices of the smart-home environment 30are modular and can be incorporated into older and new houses. Forexample, the devices 10 are designed around a modular platformconsisting of two basic components: a head unit and a back plate, whichis also referred to as a docking station. Multiple configurations of thedocking station are provided so as to be compatible with any home, suchas older and newer homes. However, all of the docking stations include astandard head-connection arrangement, such that any head unit can beremovably attached to any docking station. Thus, in some embodiments,the docking stations are interfaces that serve as physical connectionsto the structure and the voltage wiring of the homes, and theinterchangeable head units contain all of the sensors 12, processors 28,user interfaces 14, the power supply 16, the network interface 18, andother functional components of the devices described above.

Many different commercial and functional possibilities for provisioning,maintenance, and upgrade are possible. For example, after years of usingany particular head unit, a user will be able to buy a new version ofthe head unit and simply plug it into the old docking station. There arealso many different versions for the head units, such as low-costversions with few features, and then a progression ofincreasingly-capable versions, up to and including extremely fancy headunits with a large number of features. Thus, it should be appreciatedthat the various versions of the head units can all be interchangeable,with any of them working when placed into any docking station. This canadvantageously encourage sharing and re-deployment of old head units—forexample, when an important high-capability head unit, such as a hazarddetector, is replaced by a new version of the head unit, then the oldhead unit can be re-deployed to a back room or basement, etc. Accordingto embodiments, when first plugged into a docking station, the head unitcan ask the user (by 2D LCD display, 2D/3D holographic projection, voiceinteraction, etc.) a few simple questions such as, “Where am I” and theuser can indicate “living room”, “kitchen” and so forth.

The smart-home environment 30 may also include communication withdevices outside of the physical home but within a proximate geographicalrange of the home. For example, the smart-home environment 30 mayinclude a pool heater monitor 34 that communicates a current pooltemperature to other devices within the smart-home environment 30 orreceives commands for controlling the pool temperature. Similarly, thesmart-home environment 30 may include an irrigation monitor 36 thatcommunicates information regarding irrigation systems within thesmart-home environment 30 and/or receives control information forcontrolling such irrigation systems. According to embodiments, analgorithm is provided for considering the geographic location of thesmart-home environment 30, such as based on the zip code or geographiccoordinates of the home. The geographic information is then used toobtain data helpful for determining optimal times for watering, suchdata may include sun location information, temperature, dewpoint, soiltype of the land on which the home is located, etc.

By virtue of network connectivity, one or more of the smart-home devicesof FIG. 2 can further allow a user to interact with the device even ifthe user is not proximate to the device. For example, a user cancommunicate with a device using a computer (e.g., a desktop computer,laptop computer, or tablet) or other portable electronic device (e.g., asmartphone) 66. A web page or app can be configured to receivecommunications from the user and control the device based on thecommunications and/or to present information about the device'soperation to the user. For example, the user can view a current setpointtemperature for a device and adjust it using a computer. The user can bein the structure during this remote communication or outside thestructure.

As discussed, users can control the smart thermostat and other smartdevices in the smart-home environment 30 using a network-connectedcomputer or portable electronic device 66. In some examples, some or allof the occupants (e.g., individuals who live in the home) can registertheir device 66 with the smart-home environment 30. Such registrationcan be made at a central server to authenticate the occupant and/or thedevice as being associated with the home and to give permission to theoccupant to use the device to control the smart devices in the home. Anoccupant can use their registered device 66 to remotely control thesmart devices of the home, such as when the occupant is at work or onvacation. The occupant may also use their registered device to controlthe smart devices when the occupant is actually located inside the home,such as when the occupant is sitting on a couch inside the home. Itshould be appreciated that instead of or in addition to registeringdevices 66, the smart-home environment 30 makes inferences about whichindividuals live in the home and are therefore occupants and whichdevices 66 are associated with those individuals. As such, thesmart-home environment “learns” who is an occupant and permits thedevices 66 associated with those individuals to control the smartdevices of the home.

In some instances, guests desire to control the smart devices. Forexample, the smart-home environment may receive communication from anunregistered mobile device of an individual inside of the home, wheresaid individual is not recognized as an occupant of the home. Further,for example, a smart-home environment may receive communication from amobile device of an individual who is known to be or who is registeredas a guest.

According to embodiments, a guest-layer of controls can be provided toguests of the smart-home environment 30. The guest-layer of controlsgives guests access to basic controls (e.g., a judicially selectedsubset of features of the smart devices), such as temperatureadjustments, but it locks out other functionalities. The guest layer ofcontrols can be thought of as a “safe sandbox” in which guests havelimited controls, but they do not have access to more advanced controlsthat could fundamentally alter, undermine, damage, or otherwise impairthe occupant-desired operation of the smart devices. For example, theguest layer of controls will not permit the guest to adjust theheat-pump lockout temperature.

A use case example of this is when a guest is in a smart home, the guestcould walk up to the thermostat and turn the dial manually, but theguest may not want to walk around the house “hunting” for thethermostat, especially at night while the home is dark and others aresleeping. Further, the guest may not want to go through the hassle ofdownloading the necessary application to their device for remotelycontrolling the thermostat. In fact, the guest may not have the homeowner's login credentials, etc., and therefore cannot remotely controlthe thermostat via such an application. Accordingly, according toembodiments of the invention, the guest can open a mobile browser ontheir mobile device, type a keyword, such as “NEST” into the URL fieldand tap “Go” or “Search”, etc. In response, the device presents theguest with a user interface which allows the guest to move the targettemperature between a limited range, such as 65 and 80 degreesFahrenheit. As discussed, the user interface provides a guest layer ofcontrols that are limited to basic functions. The guest cannot changethe target humidity, modes, or view energy history.

According to embodiments, to enable guests to access the user interfacethat provides the guest layer of controls, a local webserver is providedthat is accessible in the local area network (LAN). It does not requirea password, because physical presence inside the home is establishedreliably enough by the guest's presence on the LAN. In some embodiments,during installation of the smart device, such as the smart thermostat,the home owner is asked if they want to enable a Local Web App (LWA) onthe smart device. Business owners will likely say no; home owners willlikely say yes. When the LWA option is selected, the smart devicebroadcasts to the LAN that the above referenced keyword, such as “NEST”,is now a host alias for its local web server. Thus, no matter whose homea guest goes to, that same keyword (e.g., “NEST”) is always the URL youuse to access the LWA, provided the smart device is purchased from thesame manufacturer. Further, according to embodiments, if there is morethan one smart device on the LAN, the second and subsequent smartdevices do not offer to set up another LWA. Instead, they registerthemselves as target candidates with the master LWA. And in this casethe LWA user would be asked which smart device they want to change thetemperature on before getting the simplified user interface for theparticular smart device they choose.

According to embodiments, a guest layer of controls may also be providedto users by means other than a device 66. For example, the smart device,such as the smart thermostat, may be equipped with walkup-identificationtechnology (e.g., face recognition, RFID, ultrasonic sensors) that“fingerprints” or creates a “signature” for the occupants of the home.The walkup-identification technology can be the same as or similar tothe fingerprinting and signature creating techniques described in othersections of this application. In operation, when a person who does notlive in the home or is otherwise not registered with the smart home orwhose fingerprint or signature is not recognized by the smart home“walks up” to a smart device, the smart device provides the guest withthe guest layer of controls, rather than full controls.

As described below, the smart thermostat 46 and other smart devices“learn” by observing occupant behavior. For example, the smartthermostat learns occupants' preferred temperature set-points formornings and evenings, and it learns when the occupants are asleep orawake, as well as when the occupants are typically away or at home, forexample. According to embodiments, when a guest controls the smartdevices, such as the smart thermostat, the smart devices do not “learn”from the guest. This prevents the guest's adjustments and controls fromaffecting the learned preferences of the occupants.

According to some embodiments, a smart television remote control isprovided. The smart remote control recognizes occupants by thumbprint,visual identification, RFID, etc., and it recognizes a user as a guestor as someone belonging to a particular class having limited control andaccess (e.g., child). Upon recognizing the user as a guest or someonebelonging to a limited class, the smart remote control only permits thatuser to view a subset of channels and to make limited adjustments to thesettings of the television and other devices. For example, a guestcannot adjust the digital video recorder (DVR) settings, and a child islimited to viewing child-appropriate programming.

According to some embodiments, similar controls are provided for otherinstruments, utilities, and devices in the house. For example, sinks,bathtubs, and showers can be controlled by smart spigots that recognizeusers as guests or as children and therefore prevent water fromexceeding a designated temperature that is considered safe.

In some embodiments, in addition to containing processing and sensingcapabilities, each of the devices 34, 36, 46, 50, 52, 54, 56, and 58(collectively referred to as “the smart devices”) is capable of datacommunications and information sharing with any other of the smartdevices, as well as to any central server or cloud-computing system orany other device that is network-connected anywhere in the world. Therequired data communications can be carried out using any of a varietyof custom or standard wireless protocols (Wi-Fi, ZigBee, 6LoWPAN, etc.)and/or any of a variety of custom or standard wired protocols (CAT6Ethernet, HomePlug, etc.).

According to embodiments, all or some of the smart devices can serve aswireless or wired repeaters. For example, a first one of the smartdevices can communicate with a second one of the smart device via awireless router 60. The smart devices can further communicate with eachother via a connection to a network, such as the Internet 62. Throughthe Internet 62, the smart devices can communicate with a central serveror a cloud-computing system 64. The central server or cloud-computingsystem 64 can be associated with a manufacturer, support entity, orservice provider associated with the device. For one embodiment, a usermay be able to contact customer support using a device itself ratherthan needing to use other communication means such as a telephone orInternet-connected computer. Further, software updates can beautomatically sent from the central server or cloud-computing system 64to devices (e.g., when available, when purchased, or at routineintervals).

According to embodiments, the smart devices combine to create a meshnetwork of spokesman and low-power nodes in the smart-home environment30, where some of the smart devices are “spokesman” nodes and others are“low-powered” nodes. Some of the smart devices in the smart-homeenvironment 30 are battery powered, while others have a regular andreliable power source, such as by connecting to wiring (e.g., to 120Vline voltage wires) behind the walls 40 of the smart-home environment.The smart devices that have a regular and reliable power source arereferred to as “spokesman” nodes. These nodes are equipped with thecapability of using any wireless protocol or manner to facilitatebidirectional communication with any of a variety of other devices inthe smart-home environment 30 as well as with the central server orcloud-computing system 64. On the other hand, the devices that arebattery powered are referred to as “low-power” nodes. These nodes tendto be smaller than spokesman nodes and can only communicate usingwireless protocols that requires very little power, such as Zigbee,6LoWPAN, etc. Further, some, but not all, low-power nodes are incapableof bidirectional communication. These low-power nodes send messages, butthey are unable to “listen”. Thus, other devices in the smart-homeenvironment 30, such as the spokesman nodes, cannot send information tothese low-power nodes.

As described, the smart devices serve as low-power and spokesman nodesto create a mesh network in the smart-home environment 30. Individuallow-power nodes in the smart-home environment regularly send outmessages regarding what they are sensing, and the other low-powerednodes in the smart-home environment—in addition to sending out their ownmessages—repeat the messages, thereby causing the messages to travelfrom node to node (i.e., device to device) throughout the smart-homeenvironment 30. The spokesman nodes in the smart-home environment 30 areable to “drop down” to low-powered communication protocols to receivethese messages, translate the messages to other communication protocols,and send the translated messages to other spokesman nodes and/or thecentral server or cloud-computing system 64. Thus, the low-powered nodesusing low-power communication protocols are able to send messages acrossthe entire smart-home environment 30 as well as over the Internet 62 tothe central server or cloud-computing system 64. According toembodiments, the mesh network enables the central server orcloud-computing system 64 to regularly receive data from all of thesmart devices in the home, make inferences based on the data, and sendcommands back to one of the smart devices to accomplish some of thesmart-home objectives described herein.

As described, the spokesman nodes and some of the low-powered nodes arecapable of “listening”. Accordingly, users, other devices, and thecentral server or cloud-computing system 64 can communicate controls tothe low-powered nodes. For example, a user can use the portableelectronic device (e.g., a smartphone) 66 to send commands over theInternet 62 to the central server or cloud-computing system 64, whichthen relays the commands to the spokesman nodes in the smart-homeenvironment 30. The spokesman nodes drop down to a low-power protocol tocommunicate the commands to the low-power nodes throughout thesmart-home environment, as well as to other spokesman nodes that did notreceive the commands directly from the central server or cloud-computingsystem 64.

An example of a low-power node is a smart night light 65. In addition tohousing a light source, the smart night light 65 houses an occupancysensor, such as an ultrasonic or passive IR sensor, and an ambient lightsensor, such as a photoresistor or a single-pixel sensor that measureslight in the room. In some embodiments, the smart night light 65 isconfigured to activate the light source when its ambient light sensordetects that the room is dark and when its occupancy sensor detects thatsomeone is in the room. In other embodiments, the smart night light 65is simply configured to activate the light source when its ambient lightsensor detects that the room is dark. Further, according to embodiments,the smart night light 65 includes a low-power wireless communicationchip (e.g., ZigBee chip) that regularly sends out messages regarding theoccupancy of the room and the amount of light in the room, includinginstantaneous messages coincident with the occupancy sensor detectingthe presence of a person in the room. As mentioned above, these messagesmay be sent wirelessly, using the mesh network, from node to node (i.e.,smart device to smart device) within the smart-home environment 30 aswell as over the Internet 62 to the central server or cloud-computingsystem 64.

Other examples of low-powered nodes include battery-operated versions ofthe smart hazard detectors 50. These smart hazard detectors 50 are oftenlocated in an area without access to constant and reliable power and, asdiscussed in detail below, may include any number and type of sensors,such as smoke/fire/heat sensors, carbon monoxide/dioxide sensors,occupancy/motion sensors, ambient light sensors, temperature sensors,humidity sensors, and the like. Furthermore, smart hazard detectors 50can send messages that correspond to each of the respective sensors tothe other devices and the central server or cloud-computing system 64,such as by using the mesh network as described above.

Examples of spokesman nodes include smart thermostats 46, smartdoorbells 52, smart wall switches 54, and smart wall plugs 56. Thesedevices 46, 52, 54, and 56 are often located near and connected to areliable power source, and therefore can include more power-consumingcomponents, such as one or more communication chips capable ofbidirectional communication in any variety of protocols.

In some embodiments, these low-powered and spokesman nodes (e.g.,devices 46, 50, 52, 54, 56, 58, and 65) can function as “tripwires” foran alarm system in the smart-home environment. For example, in the eventa perpetrator circumvents detection by alarm sensors located at windows,doors, and other entry points of the smart-home environment 30, thealarm could be triggered upon receiving an occupancy, motion, heat,sound, etc. message from one or more of the low-powered and spokesmannodes in the mesh network. For example, upon receiving a message from asmart night light 65 indicating the presence of a person, the centralserver or cloud-computing system 64 or some other device could triggeran alarm, provided the alarm is armed at the time of detection. Thus,the alarm system could be enhanced by various low-powered and spokesmannodes located throughout the smart-home environment 30. In this example,a user could enhance the security of the smart-home environment 30 bybuying and installing extra smart nightlights 65. However, in a scenariowhere the perpetrator uses a radio transceiver to jam the wirelessnetwork, the devices 10 may be incapable of communicating with eachother. Therefore, as discussed in detail below, the present techniquesprovide network communication jamming attack detection and notificationsolutions to such a problem.

In some embodiments, the mesh network can be used to automatically turnon and off lights as a person transitions from room to room. Forexample, the low-powered and spokesman nodes detect the person'smovement through the smart-home environment and communicatecorresponding messages through the mesh network. Using the messages thatindicate which rooms are occupied, the central server or cloud-computingsystem 64 or some other device activates and deactivates the smart wallswitches 54 to automatically provide light as the person moves from roomto room in the smart-home environment 30. Further, users may providepre-configuration information that indicates which smart wall plugs 56provide power to lamps and other light sources, such as the smart nightlight 65. Alternatively, this mapping of light sources to wall plugs 56can be done automatically (e.g., the smart wall plugs 56 detect when alight source is plugged into it, and it sends a corresponding message tothe central server or cloud-computing system 64). Using this mappinginformation in combination with messages that indicate which rooms areoccupied, the central server or cloud-computing system 64 or some otherdevice activates and deactivates the smart wall plugs 56 that providepower to lamps and other light sources so as to track the person'smovement and provide light as the person moves from room to room.

In some embodiments, the mesh network of low-powered and spokesman nodescan be used to provide exit lighting in the event of an emergency. Insome instances, to facilitate this, users provide pre-configurationinformation that indicates exit routes in the smart-home environment 30.For example, for each room in the house, the user provides a map of thebest exit route. It should be appreciated that instead of a userproviding this information, the central server or cloud-computing system64 or some other device could automatically determine the routes usinguploaded maps, diagrams, architectural drawings of the smart-home house,as well as using a map generated based on positional informationobtained from the nodes of the mesh network (e.g., positionalinformation from the devices is used to construct a map of the house).In operation, when an alarm is activated (e.g., when one or more of thesmart hazard detector 50 detects smoke and activates an alarm), thecentral server or cloud-computing system 64 or some other device usesoccupancy information obtained from the low-powered and spokesman nodesto determine which rooms are occupied and then turns on lights (e.g.,nightlights 65, wall switches 54, wall plugs 56 that power lamps, etc.)along the exit routes from the occupied rooms so as to provide emergencyexit lighting.

Further included and illustrated in the smart-home environment 30 ofFIG. 2 are service robots 69 each configured to carry out, in anautonomous manner, any of a variety of household tasks. For someembodiments, the service robots 69 can be respectively configured toperform floor sweeping, floor washing, etc. in a manner similar to thatof known commercially available devices such as the ROOMBA™ and SCOOBA™products sold by iRobot, Inc. of Bedford, Mass. Tasks such as floorsweeping and floor washing can be considered as “away” or “while-away”tasks for purposes of the instant description, as it is generally moredesirable for these tasks to be performed when the occupants are notpresent. For other embodiments, one or more of the service robots 69 areconfigured to perform tasks such as playing music for an occupant,serving as a localized thermostat for an occupant, serving as alocalized air monitor/purifier for an occupant, serving as a localizedbaby monitor, serving as a localized hazard detector for an occupant,and so forth, it being generally more desirable for such tasks to becarried out in the immediate presence of the human occupant. Forpurposes of the instant description, such tasks can be considered as“human-facing” or “human-centric” tasks.

When serving as a localized thermostat for an occupant, a particular oneof the service robots 69 can be considered to be facilitating what canbe called a “personal comfort-area network” for the occupant, with theobjective being to keep the occupant's immediate space at a comfortabletemperature wherever that occupant may be located in the home. This canbe contrasted with conventional wall-mounted room thermostats, whichhave the more attenuated objective of keeping a statically-definedstructural space at a comfortable temperature. According to oneembodiment, the localized-thermostat service robot 69 is configured tomove itself into the immediate presence (e.g., within five feet) of aparticular occupant who has settled into a particular location in thehome (e.g. in the dining room to eat their breakfast and read the news).The localized-thermostat service robot 69 includes a temperature sensor,a processor, and wireless communication components configured such thatcontrol communications with the HVAC system, either directly or througha wall-mounted wirelessly communicating thermostat coupled to the HVACsystem, are maintained and such that the temperature in the immediatevicinity of the occupant is maintained at their desired level. If theoccupant then moves and settles into another location (e.g. to theliving room couch to watch television), the localized-thermostat servicerobot 69 proceeds to move and park itself next to the couch and keepthat particular immediate space at a comfortable temperature.

Technologies by which the localized-thermostat service robot 69 (and/orthe larger smart-home system of FIG. 2) can identify and locate theoccupant whose personal-area space is to be kept at a comfortabletemperature can include, but are not limited to, RFID sensing (e.g.,person having an RFID bracelet, RFID necklace, or RFID key fob),synthetic vision techniques (e.g., video cameras and face recognitionprocessors), audio techniques (e.g., voice, sound pattern, vibrationpattern recognition), ultrasound sensing/imaging techniques, andinfrared or near-field communication (NFC) techniques (e.g., personwearing an infrared or NFC-capable smartphone), along with rules-basedinference engines or artificial intelligence techniques that draw usefulconclusions from the sensed information (e.g., if there is only a singleoccupant present in the home, then that is the person whose immediatespace should be kept at a comfortable temperature, and the selection ofthe desired comfortable temperature should correspond to that occupant'sparticular stored profile).

When serving as a localized air monitor/purifier for an occupant, aparticular service robot 69 can be considered to be facilitating whatcan be called a “personal health-area network” for the occupant, withthe objective being to keep the air quality in the occupant's immediatespace at healthy levels. Alternatively or in conjunction therewith,other health-related functions can be provided, such as monitoring thetemperature or heart rate of the occupant (e.g., using finely remotesensors, near-field communication with on-person monitors, etc.). Whenserving as a localized hazard detector for an occupant, a particularservice robot 69 can be considered to be facilitating what can be calleda “personal safety-area network” for the occupant, with the objectivebeing to ensure there is no excessive carbon monoxide, smoke, fire,etc., in the immediate space of the occupant. Methods analogous to thosedescribed above for personal comfort-area networks in terms of occupantidentifying and tracking are likewise applicable for personalhealth-area network and personal safety-area network embodiments.

According to some embodiments, the above-referenced facilitation ofpersonal comfort-area networks, personal health-area networks, personalsafety-area networks, and/or other such human-facing functionalities ofthe service robots 69, are further enhanced by logical integration withother smart sensors in the home according to rules-based inferencingtechniques or artificial intelligence techniques for achieving betterperformance of those human-facing functionalities and/or for achievingthose goals in energy-conserving or other resource-conserving ways.Thus, for one embodiment relating to personal health-area networks, theair monitor/purifier service robot 69 can be configured to detectwhether a household pet is moving toward the currently settled locationof the occupant (e.g., using on-board sensors and/or by datacommunications with other smart-home sensors along with rules-basedinferencing/artificial intelligence techniques), and if so, the airpurifying rate is immediately increased in preparation for the arrivalof more airborne pet dander. For another embodiment relating to personalsafety-area networks, the hazard detector service robot 69 can beadvised by other smart-home sensors that the temperature and humiditylevels are rising in the kitchen, which is nearby to the occupant'scurrent dining room location, and responsive to this advisory the hazarddetector service robot 69 will temporarily raise a hazard detectionthreshold, such as a smoke detection threshold, under an inference thatany small increases in ambient smoke levels will most likely be due tocooking activity and not due to a genuinely hazardous condition.

The above-described “human-facing” and “away” functionalities can beprovided, without limitation, by multiple distinct service robots 69having respective dedicated ones of such functionalities, by a singleservice robot 69 having an integration of two or more different ones ofsuch functionalities, and/or any combinations thereof (including theability for a single service robot 69 to have both “away” and “humanfacing” functionalities) without departing from the scope of the presentteachings. Electrical power can be provided by virtue of rechargeablebatteries or other rechargeable methods, such as an out-of-the-waydocking station to which the service robots 69 will automatically dockand recharge its batteries (if needed) during periods of inactivity.Preferably, each service robot 69 includes wireless communicationcomponents that facilitate data communications with one or more of theother wirelessly communicating smart-home sensors of FIG. 2 and/or withone or more other service robots 69 (e.g., using Wi-Fi, Zigbee, Z-Wave,6LoWPAN, etc.), and one or more of the smart-home devices 10 can be incommunication with a remote server over the Internet. Alternatively orin conjunction therewith, each service robot 69 can be configured tocommunicate directly with a remote server by virtue of cellulartelephone communications, satellite communications, 3G/4G network datacommunications, or other direct communication method.

Provided according to some embodiments are systems and methods relatingto the integration of the service robot(s) 69 with home security sensorsand related functionalities of the smart home system. The embodimentsare particularly applicable and advantageous when applied for thoseservice robots 69 that perform “away” functionalities or that otherwiseare desirable to be active when the home is unoccupied (hereinafter“away-service robots”). Included in the embodiments are methods andsystems for ensuring that home security systems, intrusion detectionsystems, and/or occupancy-sensitive environmental control systems (forexample, occupancy-sensitive automated setback thermostats that enterinto a lower-energy-using condition when the home is unoccupied) are noterroneously triggered by the away-service robots.

Provided according to one embodiment is a home automation and securitysystem (e.g., as shown in FIG. 2) that is remotely monitored by amonitoring service by virtue of automated systems (e.g., cloud-basedservers or other central servers, hereinafter “central server”) that arein data communications with one or more network-connected elements ofthe home automation and security system. The away-service robots areconfigured to be in operative data communication with the centralserver, and are configured such that they remain in a non-away-servicestate (e.g., a dormant state at their docking station) unless permissionis granted from the central server (e.g., by virtue of an“away-service-OK” message from the central server) to commence theiraway-service activities. An away-state determination made by the system,which can be arrived at (i) exclusively by local on-premises smartdevice(s) based on occupancy sensor data, (ii) exclusively by thecentral server based on received occupancy sensor data and/or based onreceived proximity-related information such as GPS coordinates from usersmartphones or automobiles, or (iii) any combination of (i) and (ii) canthen trigger the granting of away-service permission to the away-servicerobots by the central server. During the course of the away-servicerobot activity, during which the away-service robots may continuouslydetect and send their in-home location coordinates to the centralserver, the central server can readily filter signals from the occupancysensing devices to distinguish between the away-service robot activityversus any unexpected intrusion activity, thereby avoiding a falseintrusion alarm condition while also ensuring that the home is secure.Alternatively or in conjunction therewith, the central server mayprovide filtering data (such as an expected occupancy-sensing profiletriggered by the away-service robots) to the occupancy sensing nodes orassociated processing nodes of the smart home, such that the filteringis performed at the local level. Although somewhat less secure, it wouldalso be within the scope of the present teachings for the central serverto temporarily disable the occupancy sensing equipment for the durationof the away-service robot activity.

According to another embodiment, functionality similar to that of thecentral server in the above example can be performed by an on-sitecomputing device such as a dedicated server computer, a “master” homeautomation console or panel, or as an adjunct function of one or more ofthe smart-home devices of FIG. 2. In such an embodiment, there would beno dependency on a remote service provider to provide the“away-service-OK” permission to the away-service robots and thefalse-alarm-avoidance filtering service or filter information for thesensed intrusion detection signals.

According to other embodiments, there are provided methods and systemsfor implementing away-service robot functionality while avoiding falsehome security alarms and false occupancy-sensitive environmentalcontrols without the requirement of a single overall event orchestrator.For purposes of the simplicity in the present disclosure, the homesecurity systems and/or occupancy-sensitive environmental controls thatwould be triggered by the motion, noise, vibrations, or otherdisturbances of the away-service robot activity are referenced simply as“activity sensing systems,” and when so triggered will yield a“disturbance-detected” outcome representative of the false trigger (forexample, an alarm message to a security service, or an “arrival”determination for an automated setback thermostat that causes the hometo be heated or cooled to a more comfortable “occupied” setpointtemperature). According to one embodiment, the away-service robots areconfigured to emit a standard ultrasonic sound throughout the course oftheir away-service activity, the activity sensing systems are configuredto detect that standard ultrasonic sound, and the activity sensingsystems are further configured such that no disturbance-detected outcomewill occur for as long as that standard ultrasonic sound is detected.For other embodiments, the away-service robots are configured to emit astandard notification signal throughout the course of their away-serviceactivity, the activity sensing systems are configured to detect thatstandard notification signal, and the activity sensing systems arefurther configured such that no disturbance-detected outcome will occurfor as long as that standard notification signal is detected, whereinthe standard notification signal comprises one or more of: an opticalnotifying signal; an audible notifying signal; an infrared notifyingsignal; an infrasonic notifying signal; a wirelessly transmitted datanotification signal (e.g., an IP broadcast, multicast, or unicastnotification signal, or a notification message sent in an TCP/IP two-waycommunication session).

According to some embodiments, the notification signals sent by theaway-service robots to the activity sensing systems are authenticatedand encrypted such that the notifications cannot be learned andreplicated by a potential burglar. Any of a variety of knownencryption/authentication schemes can be used to ensure such datasecurity including, but not limited to, methods involving third partydata security services or certificate authorities. For some embodiments,a permission request-response model can be used, wherein any particularaway-service robot requests permission from each activity sensing systemin the home when it is ready to perform its away-service tasks, and doesnot initiate such activity until receiving a “yes” or “permissiongranted” message from each activity sensing system (or from a singleactivity sensing system serving as a “spokesman” for all of the activitysensing systems). One advantage of the described embodiments that do notrequire a central event orchestrator is that there can (optionally) bemore of an arms-length relationship between the supplier(s) of the homesecurity/environmental control equipment, on the one hand, and thesupplier(s) of the away-service robot(s), on the other hand, as it isonly required that there is the described standard one-way notificationprotocol or the described standard two-way request/permission protocolto be agreed upon by the respective suppliers.

According to still other embodiments, the activity sensing systems areconfigured to detect sounds, vibrations, RF emissions, or otherdetectable environmental signals or “signatures” that are intrinsicallyassociated with the away-service activity of each away-service robot,and are further configured such that no disturbance-detected outcomewill occur for as long as that particular detectable signal orenvironmental “signature” is detected. By way of example, a particularkind of vacuum-cleaning away-service robot may emit a specific sound orRF signature. For one embodiment, the away-service environmentalsignatures for each of a plurality of known away-service robots arestored in the memory of the activity sensing systems based onempirically collected data, the environmental signatures being suppliedwith the activity sensing systems and periodically updated by a remoteupdate server. For another embodiment, the activity sensing systems canbe placed into a “training mode” for the particular home in which theyare installed, wherein they “listen” and “learn” the particularenvironmental signatures of the away-service robots for that home duringthat training session, and thereafter will suppress disturbance-detectedoutcomes for intervals in which those environmental signatures areheard.

For still another embodiment, which is particularly useful when theactivity sensing system is associated with occupancy-sensitiveenvironmental control equipment rather than a home security system, theactivity sensing system is configured to automatically learn theenvironmental signatures for the away-service robots by virtue ofautomatically performing correlations over time between detectedenvironmental signatures and detected occupancy activity. By way ofexample, for one embodiment an intelligent automatednonoccupancy-triggered setback thermostat such as the Nest LearningThermostat can be configured to constantly monitor for audible and RFactivity as well as to perform infrared-based occupancy detection. Inparticular view of the fact that the environmental signature of theaway-service robot will remain relatively constant from event to event,and in view of the fact that the away-service events will likely either(a) themselves be triggered by some sort of nonoccupancy condition asmeasured by the away-service robots themselves, or (b) occur at regulartimes of day, there will be patterns in the collected data by which theevents themselves will become apparent and for which the environmentalsignatures can be readily learned. Generally speaking, for thisautomatic-learning embodiment in which the environmental signatures ofthe away-service robots are automatically learned without requiring userinteraction, it is more preferable that a certain number of falsetriggers be tolerable over the course of the learning process.Accordingly, this automatic-learning embodiment is more preferable forapplication in occupancy-sensitive environmental control equipment (suchas an automated setback thermostat) rather than home security systemsfor the reason that a few false occupancy determinations may cause a fewinstances of unnecessary heating or cooling, but will not otherwise haveany serious consequences, whereas false home security alarms may havemore serious consequences.

According to embodiments, technologies including the sensors of thesmart devices located in the mesh network of the smart-home environmentin combination with rules-based inference engines or artificialintelligence provided at the central server or cloud-computing system 64are used to provide a personal “smart alarm clock” for individualoccupants of the home. For example, user-occupants can communicate withthe central server or cloud-computing system 64 via their mobile devices66 to access an interface for the smart alarm clock. There, occupantscan turn on their “smart alarm clock” and input a wake time for the nextday and/or for additional days. In some embodiments, the occupant mayhave the option of setting a specific wake time for each day of theweek, as well as the option of setting some or all of the inputted waketimes to “repeat”. Artificial intelligence will be used to consider theoccupant's response to these alarms when they go off and make inferencesabout the user's preferred sleep patterns over time.

According to embodiments, the smart device in the smart-home environment30 that happens to be closest to the occupant when the occupant fallsasleep will be the device that transmits messages regarding when theoccupant stopped moving, from which the central server orcloud-computing system 64 will make inferences about where and when theoccupant prefers to sleep. This closest smart device will as be thedevice that sounds the alarm to wake the occupant. In this manner, the“smart alarm clock” will follow the occupant throughout the house, bytracking the individual occupants based on their “unique signature”,which is determined based on data obtained from sensors located in thesmart devices. For example, the sensors include ultrasonic sensors,passive IR sensors, and the like. The unique signature is based on acombination of walking gate, patterns of movement, voice, height, size,etc. It should be appreciated that facial recognition may also be used.

According to an embodiment, the wake times associated with the “smartalarm clock” are used by the smart thermostat 46 to control the HVAC inan efficient manner so as to pre-heat or cool the house to theoccupant's desired “sleeping” and “awake” temperature settings. Thepreferred settings can be learned over time, such as by observing whichtemperature the occupant sets the thermostat to before going to sleepand which temperature the occupant sets the thermostat to upon wakingup.

According to an embodiment, a device is positioned proximate to theoccupant's bed, such as on an adjacent nightstand, and collects data asthe occupant sleeps using noise sensors, motion sensors (e.g.,ultrasonic, IR, and optical), etc. Data may be obtained by the othersmart devices in the room as well. Such data may include the occupant'sbreathing patterns, heart rate, movement, etc. Inferences are made basedon this data in combination with data that indicates when the occupantactually wakes up. For example, if—on a regular basis—the occupant'sheart rate, breathing, and moving all increase by 5% to 10%, twenty tothirty minutes before the occupant wakes up each morning, thenpredictions can be made regarding when the occupant is going to wake.Other devices in the home can use these predictions to provide othersmart-home objectives, such as adjusting the smart thermostat 46 so asto pre-heat or cool the home to the occupant's desired setting beforethe occupant wakes up. Further, these predictions can be used to set the“smart alarm clock” for the occupant, to turn on lights, etc.

According to embodiments, technologies including the sensors of thesmart devices located throughout the smart-home environment incombination with rules-based inference engines or artificialintelligence provided at the central server or cloud-computing system 64are used to detect or monitor the progress of Alzheimer's Disease. Forexample, the unique signatures of the occupants are used to track theindividual occupants' movement throughout the smart-home environment 30.This data can be aggregated and analyzed to identify patterns indicativeof Alzheimer's. Oftentimes, individuals with Alzheimer's havedistinctive patterns of migration in their homes. For example, a personwill walk to the kitchen and stand there for a while, then to the livingroom and stand there for a while, and then back to the kitchen. Thispattern will take about thirty minutes, and then the person will repeatthe pattern. According to embodiments, the remote servers or cloudcomputing architectures 64 analyze the person's migration data collectedby the mesh network of the smart-home environment to identify suchpatterns.

In addition, FIG. 3 illustrates an embodiment of an extensible devicesand services platform 80 that can be concentrated at a single server ordistributed among several different computing entities withoutlimitation with respect to the smart-home environment 30. The extensibledevices and services platform 80 may include a processing engine 86,which may include engines that receive data from devices of smart-homeenvironments (e.g., via the Internet or a hubbed network), to index thedata, to analyze the data and/or to generate statistics based on theanalysis or as part of the analysis. The analyzed data can be stored asderived home data 88.

Results of the analysis or statistics can thereafter be transmitted backto the device that provided home data used to derive the results, toother devices, to a server providing a web page to a user of the device,or to other non-device entities. For example, use statistics, usestatistics relative to use of other devices, use patterns, and/orstatistics summarizing sensor readings can be generated by theprocessing engine 86 and transmitted. The results or statistics can beprovided via the Internet 62. In this manner, the processing engine 86can be configured and programmed to derive a variety of usefulinformation from the home data 82. A single server can include one ormore engines.

The derived data can be highly beneficial at a variety of differentgranularities for a variety of useful purposes, ranging from explicitprogrammed control of the devices on a per-home, per-neighborhood, orper-region basis (for example, demand-response programs for electricalutilities), to the generation of inferential abstractions that canassist on a per-home basis (for example, an inference can be drawn thatthe homeowner has left for vacation and so security detection equipmentcan be put on heightened sensitivity), to the generation of statisticsand associated inferential abstractions that can be used for governmentor charitable purposes. For example, processing engine 86 can generatestatistics about device usage across a population of devices and sendthe statistics to device users, service providers or other entities(e.g., that have requested or may have provided monetary compensationfor the statistics).

According to some embodiments, the home data 82, the derived home data88, and/or another data can be used to create “automated neighborhoodsafety networks.” For example, in the event the central server orcloud-computing architecture 64 receives data indicating that aparticular home has been broken into, is experiencing a fire, or someother type of emergency event, an alarm is sent to other smart homes inthe “neighborhood.” In some instances, the central server orcloud-computing architecture 64 automatically identifies smart homeswithin a radius of the home experiencing the emergency and sends analarm to the identified homes. In such instances, the other homes in the“neighborhood” do not have to sign up for or register to be a part of asafety network, but instead are notified of an emergency based on theirproximity to the location of the emergency. This creates robust andevolving neighborhood security watch networks, such that if one person'shome is getting broken into, an alarm can be sent to nearby homes, suchas by audio announcements via the smart devices located in those homes.It should be appreciated that this can be an opt-in service and that, inaddition to or instead of the central server or cloud-computingarchitecture 64 selecting which homes to send alerts to, individuals cansubscribe to participate in such networks and individuals can specifywhich homes they want to receive alerts from. This can include, forexample, the homes of family members who live in different cities, suchthat individuals can receive alerts when their loved ones in otherlocations are experiencing an emergency.

According to some embodiments, sound, vibration, and/or motion sensingcomponents of the smart devices are used to detect sound, vibration,and/or motion created by running water. Based on the detected sound,vibration, and/or motion, the central server or cloud-computingarchitecture 64 makes inferences about water usage in the home andprovides related services. For example, the central server orcloud-computing architecture 64 can run programs/algorithms thatrecognize what water sounds like and when it is running in the home.According to one embodiment, to map the various water sources of thehome, upon detecting running water, the central server orcloud-computing architecture 64 sends a message an occupant's mobiledevice asking if water is currently running or if water has beenrecently run in the home and, if so, which room and whichwater-consumption appliance (e.g., sink, shower, toilet, etc.) was thesource of the water. This enables the central server or cloud-computingarchitecture 64 to determine the “signature” or “fingerprint” of eachwater source in the home. This is sometimes referred to herein as “audiofingerprinting water usage.”

In one illustrative example, the central server or cloud-computingarchitecture 64 creates a signature for the toilet in the masterbathroom, and whenever that toilet is flushed, the central server orcloud-computing architecture 64 will know that the water usage at thattime is associated with that toilet. Thus, the central server orcloud-computing architecture 64 can track the water usage of that toiletas well as each water-consumption application in the home. Thisinformation can be correlated to water bills or smart water meters so asto provide users with a breakdown of their water usage.

According to some embodiments, sound, vibration, and/or motion sensingcomponents of the smart devices are used to detect sound, vibration,and/or motion created by mice and other rodents as well as by termites,cockroaches, and other insects (collectively referred to as “pests”).Based on the detected sound, vibration, and/or motion, the centralserver or cloud-computing architecture 64 makes inferences aboutpest-detection in the home and provides related services. For example,the central server or cloud-computing architecture 64 can runprograms/algorithms that recognize what certain pests sound like, howthey move, and/or the vibration they create, individually and/orcollectively. According to one embodiment, the central server orcloud-computing architecture 64 can determine the “signatures” ofparticular types of pests.

For example, in the event the central server or cloud-computingarchitecture 64 detects sounds that may be associated with pests, itnotifies the occupants of such sounds and suggests hiring a pest controlcompany. If it is confirmed that pests are indeed present, the occupantsinput to the central server or cloud-computing architecture 64 confirmsthat its detection was correct, along with details regarding theidentified pests, such as name, type, description, location, quantity,etc. This enables the central server or cloud-computing architecture 64to “tune” itself for better detection and create “signatures” or“fingerprints” for specific types of pests. For example, the centralserver or cloud-computing architecture 64 can use the tuning as well asthe signatures and fingerprints to detect pests in other homes, such asnearby homes that may be experiencing problems with the same pests.Further, for example, in the event that two or more homes in a“neighborhood” are experiencing problems with the same or similar typesof pests, the central server or cloud-computing architecture 64 can makeinferences that nearby homes may also have such problems or may besusceptible to having such problems, and it can send warning messages tothose homes to help facilitate early detection and prevention.

In some embodiments, to encourage innovation and research and toincrease products and services available to users, the devices andservices platform 80 expose a range of application programminginterfaces (APIs) 90 to third parties, such as charities 94,governmental entities 96 (e.g., the Food and Drug Administration or theEnvironmental Protection Agency), academic institutions 98 (e.g.,university researchers), businesses 100 (e.g., providing devicewarranties or service to related equipment, targeting advertisementsbased on home data), utility companies 102, and other third parties. TheAPIs 90 are coupled to and permit third party systems to communicatewith the central server or the cloud-computing system 64, including theservices 84, the processing engine 86, the home data 82, and the derivedhome data 88. For example, the APIs 90 allow applications executed bythe third parties to initiate specific data processing tasks that areexecuted by the central server or the cloud-computing system 64, as wellas to receive dynamic updates to the home data 82 and the derived homedata 88.

For example, third parties can develop programs and/or applications,such as web or mobile apps that integrate with the central server or thecloud-computing system 64 to provide services and information to users.Such programs and application may be, for example, designed to helpusers reduce energy consumption, to preemptively service faultyequipment, to prepare for high service demands, to track past serviceperformance, etc., or to perform any of a variety of beneficialfunctions or tasks now known or hereinafter developed.

According to some embodiments, third party applications make inferencesfrom the home data 82 and the derived home data 88, such inferences mayinclude when are occupants home, when are they sleeping, when are theycooking, when are they in the den watching television, and when do theyshower. The answers to these questions may help third-parties benefitconsumers by providing them with interesting information, products andservices as well as with providing them with targeted advertisements.

In one example, a shipping company creates an application that makesinferences regarding when people are at home. The application uses theinferences to schedule deliveries for times when people will most likelybe at home. The application can also build delivery routes around thesescheduled times. This reduces the number of instances where the shippingcompany has to make multiple attempts to deliver packages, and itreduces the number of times consumers have to pick up their packagesfrom the shipping company.

To further illustrate, FIG. 4 describes an abstracted functional view110 of the extensible devices and services platform 80 of FIG. 3, withparticular reference to the processing engine 86 as well as devices,such as those of the smart-home environment 30 of FIG. 2. Even thoughdevices situated in smart-home environments will have an endless varietyof different individual capabilities and limitations, they can all bethought of as sharing common characteristics in that each of them is adata consumer 112 (DC), a data source 114 (DS), a services consumer 116(SC), and a services source 118 (SS). Advantageously, in addition toproviding the essential control information needed for the devices toachieve their local and immediate objectives, the extensible devices andservices platform 80 can also be configured to harness the large amountof data that is flowing out of these devices. In addition to enhancingor optimizing the actual operation of the devices themselves withrespect to their immediate functions, the extensible devices andservices platform 80 can be directed to “repurposing” that data in avariety of automated, extensible, flexible, and/or scalable ways toachieve a variety of useful objectives. These objectives may bepredefined or adaptively identified based on, e.g., usage patterns,device efficiency, and/or user input (e.g., requesting specificfunctionality).

For example, FIG. 4 shows processing engine 86 as including a number ofparadigms 120. Processing engine 86 can include a managed servicesparadigm 120 a that monitors and manages primary or secondary devicefunctions. The device functions can include ensuring proper operation ofa device given user inputs, estimating that (e.g., and responding to aninstance in which) an intruder is or is attempting to be in a dwelling,detecting a failure of equipment coupled to the device (e.g., a lightbulb having burned out), implementing or otherwise responding to energydemand response events, or alerting a user of a current or predictedfuture event or characteristic. Processing engine 86 can further includean advertising/communication paradigm 120 b that estimatescharacteristics (e.g., demographic information), desires and/or productsof interest of a user based on device usage. Services, promotions,products or upgrades can then be offered or automatically provided tothe user. Processing engine 86 can further include a social paradigm 120c that uses information from a social network, provides information to asocial network (for example, based on device usage), and/or processesdata associated with user and/or device interactions with the socialnetwork platform. For example, a user's status as reported to theirtrusted contacts on the social network could be updated to indicate whenthey are home based on light detection, security system inactivation ordevice usage detectors. As another example, a user may be able to sharedevice-usage statistics with other users. In yet another example, a usermay share HVAC settings that result in low power bills and other usersmay download the HVAC settings to their smart thermostat 46 to reducetheir power bills.

The processing engine 86 can include achallenges/rules/compliance/rewards paradigm 120 d that informs a userof challenges, competitions, rules, compliance regulations and/orrewards and/or that uses operation data to determine whether a challengehas been met, a rule or regulation has been complied with and/or areward has been earned. The challenges, rules or regulations can relateto efforts to conserve energy, to live safely (e.g., reducing exposureto toxins or carcinogens), to conserve money and/or equipment life, toimprove health, etc. For example, one challenge may involve participantsturning down their thermostat by one degree for one week. Those thatsuccessfully complete the challenge are rewarded, such as by coupons,virtual currency, status, etc. Regarding compliance, an example involvesa rental-property owner making a rule that no renters are permitted toaccess certain owner's rooms. The devices in the room having occupancysensors could send updates to the owner when the room is accessed.

The processing engine 86 can integrate or otherwise utilize extrinsicinformation 122 from extrinsic sources to improve the functioning of oneor more processing paradigms. Extrinsic information 122 can be used tointerpret data received from a device, to determine a characteristic ofthe environment near the device (e.g., outside a structure that thedevice is enclosed in), to determine services or products available tothe user, to identify a social network or social-network information, todetermine contact information of entities (e.g., public-service entitiessuch as an emergency-response team, the police or a hospital) near thedevice, etc., to identify statistical or environmental conditions,trends or other information associated with a home or neighborhood, andso forth.

An extraordinary range and variety of benefits can be brought about by,and fit within the scope of, the described extensible devices andservices platform 80, ranging from the ordinary to the profound. Thus,in one “ordinary” example, each bedroom of the smart-home environment 30can be provided with a smart wall switch 54, a smart wall plug 56,and/or smart hazard detectors 50, all or some of which include anoccupancy sensor, wherein the occupancy sensor is also capable ofinferring (e.g., by virtue of motion detection, facial recognition,audible sound patterns, etc.) whether the occupant is asleep or awake.If a serious fire event is sensed, the remote security/monitoringservice or fire department is advised of how many occupants there are ineach bedroom, and whether those occupants are still asleep (or immobile)or whether they have properly evacuated the bedroom. While this is, ofcourse, a very advantageous capability accommodated by the describedextensible devices and services platform 80, there can be substantiallymore “profound” examples that can truly illustrate the potential of alarger “intelligence” that can be made available. By way of perhaps amore “profound” example, the same bedroom occupancy data that is beingused for fire safety can also be “repurposed” by the processing engine86 in the context of a social paradigm of neighborhood child developmentand education. Thus, for example, the same bedroom occupancy and motiondata discussed in the “ordinary” example can be collected and madeavailable (properly anonymized) for processing in which the sleeppatterns of schoolchildren in a particular ZIP code can be identifiedand tracked. Localized variations in the sleeping patterns of theschoolchildren may be identified and correlated, for example, todifferent nutrition programs in local schools.

As previously discussed, the described extensible devices and servicesplatform 80 may enable communicating emergency information betweensmart-home environments 30 that are linked and/or to the properauthorities. For example, when a burglar breaks into a smart-homeenvironment 30, a home security system may trip and sound an alarmand/or send emergency notifications to the neighbors, the police, thesecurity company, and the like. However, in instances where the break inis preceded by a jamming attack on the wireless network, thenotifications may not be sent out if their transmission is dependentupon the wireless network. Thus, another means to communicate withexternal parties may be desired. As such, the techniques disclosedherein solve this problem by detecting the jamming attack and sendingemergency notifications via side channels that are not dependent uponthe wireless network.

API

Although programs, applications, and/or application services may be usedto communicate requests or commands to the smart home devices 10, insome embodiments these may not be sent directly to the smart homedevices 10. The following figures illustrate smart device communicationand/or control via an application accessing an API.

For example, FIG. 5 illustrates a system 140 where an API may be used toaccess and/or control one or more smart devices. In the illustratedexample, a person may desire to access a number of smart home devices10, such as a first smart home device (e.g. thermostat 10A) and secondsmart home devices (e.g., Smoke and/or CO detector 10B). In the exampleof FIG. 5, the first smart home device 10A is an example of a smartthermostat, such as the Nest® Learning Thermostat by Nest Labs, Inc. (acompany of Google Inc.), and the second smart home devices 10B areexamples of smart hazard detectors, such as the Nest® Protect by NestLabs, Inc. Two application programs are shown accessing the smart homedevices 10A and/or 10B through the device service 84. Although FIG. 5illustrates accessing the smart home devices 10A and/or 10B using twoseparate application programs, it should be appreciated that anysuitable number of application programs may be used to access the smarthome devices 10A and/or 10B.

In the example of FIG. 5, a first application 142 sends a first devicerequest message 144 targeted to a smart home device 10 (e.g., the smarthome device 10A) into cloud service(s) 145 and, more specifically, to afirst application service 146. A second application 148 may be used toissue a second device request message 150 targeted to a smart homedevice 10 (e.g., the smart home device 10A) to a second applicationservice 152 also among the cloud service(s) 145. In the example shown,the first application 142 is a navigation application that sendsestimated-time-of-arrival (ETA) information in the device requestmessages 144. By sending a number of ETA messages as the device requestmessages 144, the first application 142 may be used to cause the smarthome devices 10A and/or 10B to be prepared when a person arrives home.Thus, as an example, the first application 142 may send occasionaldevice request messages 144 indicating the ETA to the first applicationservice 146, which may forward this information to the device service 84(e.g., via an API, as discussed above). The device service 84 may holdthe device request messages 144 from the first application 142 until anappropriate time. In the illustrated example, the second application 148may be a third party home-automation application that may be running ona portable electronic device, such as a personal mobile device. Thesecond application 148 may generate device request messages 150, such ascommands to control or request information from the smart home devices10A and/or 10B. The second application service 152 may interface withthe device service 84 by way of an API, as mentioned above.

Although the first application service 146, the second applicationservice 152, and the device service 84 are illustrated in FIG. 5 ascloud service(s) 145, it may appreciated that some or all of theseservices may run on electronic devices that are not remotecloud-computer systems accessible by way of the Internet. Indeed, insome examples, the device service 84 may not be on a network that isremote from the smart home devices 10A and/or 10B, but rather may berunning on an electronic device in the same local area network as thesmart home devices 10A and/or 10B. For example, the device service 84may, additionally or alternatively, run on a local server computerand/or a local wireless router on the same local area network as thesmart home devices 10A and/or 10B. Moreover, some applications maycommunicate directly with the device service 84 (e.g., via the API)without first communicating with an application service such as thefirst application service 146 or the second application service 152.

Regardless of the number of applications that may issue device requestmessages (e.g., 144 or 150) to the device service 84, the device service84 may not merely forward these messages to the smart home devices 10Aand/or 10B that the device request messages are targeted too. Rather,the device service 84 may serve as the point of contact that applicationprograms may use to access the smart home devices 10A and/or 10B. Thedevice service 84 then may communicate information and/or commandsprovided by the applications to the smart home devices 10A and/or 10B,enabling coordination between the applications and the devices 10Aand/or 10B.

In some embodiments, to enable additional functionalities in theapplications (e.g., first application 142 and/or second application148), the smart home devices 10A and/or 10B may occasionally transmitdevice operation status parameters 156 or other data based on the deviceoperation status parameters 156 through the device service 84 and theproper application service (e.g., first application service 146 and/orsecond application service 152) to the proper applications (e.g., firstapplication 142 and/or second application 148).

The device operation status parameters 156 may represent any suitablecharacteristics of the operation status of the smart home devices 10Aand/or 10B that may affect the proper functioning of the smart homedevices 10A and/or 10B. Thus, the device operation status parameters 156may include, for example: a battery level 159 indicative of an amount ofcharge remaining in a battery of the smart home device; a charging rate160 indicative of a current rate that the battery of the smart homedevice is charging; a current device age 161 indicative of a period ofuse since initial install, a period of use since manufacture, a periodof use since original sale, etc.; a planned lifespan 162 indicative ofan expected useful operational duration of the smart home device; anamount of recent wireless use 163 (selected within a timespan recentenough to substantially affect an internal temperature of the smart homedevice 10); a direct measurement of an internal device temperature 164;and/or device operation status parameters for connected devices 165. Theoperational status parameters for connected devices 165 may representany suitable operational parameters that may describe the smart homedevices 10 (e.g., smart home device 10A) through which the deviceservice 84 may use to connect to a target smart home device 10 (e.g.,one of the smart home devices 10B). For example, regarding theoperational status parameters for connected devices 165, if the targetsmart home device 10 is the last smart home device 10B through threesmart home devices 10 in three communication “hops”, the deviceoperation status parameters 156 associated with these three interveningsmart home devices 10 may be included.

The various specific device operation status parameters 156 shown inFIG. 5 are provided by way of example. As such, the device operationstatus parameters 156 shown in FIG. 5 should not be understood to beexhaustive, but merely representative of possible operational parametersthat may be considered for API-accessing applications. For example,additional device operation status parameters may include current stateof the device (e.g., sleeping, awake, Wifi active/inactive, executing ademand-response algorithm, executing a time-to-temperature algorithm,etc.).

The smart thermostat 10A and/or detector 10B may include a basic set ofidentifying information, such as: a user-defined device name, physicallocation in the structure, locale, software version and containingstructure. The data model also exposes thermostat capabilities, such aswhether the HVAC system can heat or cool, or has a fan. Further, thethermostat 10A may include three states related to presence: home, awayor auto-away. In some embodiments, the API 90 may not expose thethermostat state, but may depend on this state when using thermostatmode to set target temperature. Thermostat 10A mode may have three “on”states (heat, cool, heat-cool) and one “off” state. The most common maybe “on” (home). In this mode the thermostat 10A will try to keep thestructure at a target temperature. A thermostat 10A can also be in awaymode, which is entered when no motion is sensed in the house or when theuser explicitly sets the structure to away. In this mode, it willactivate the HVAC system if the temperature moves outside the defined“away” temperature range. The thermostat 10A may also be set to “off”.In this mode it will only activate the HVAC system if the temperaturemoves outside a defined safety temperature range.

In some embodiments, target temperature, the desired temperature,typically set by the user may be modified using the API 90. From the API90, applications can write the target temperature as part of a largerprocess.

For example, the applications may use the device operation statusparameters 156 or data to affect subsequent interactions (e.g., viamessages 144 or 150) that are transmitted to the smart home devices 10Aand/or 10B. The device operation status parameters 156 may correspondonly to a target smart home device 10 (e.g., the smart home device 10A),or may correspond to other smart home devices 10 that are in thevicinity of the target smart home device 10 (e.g., the smart home device10A and the smart home devices 10B). In one example, when the targetsmart home device 10 for the device request messages 144 and/or 150 arethe smart home device 10A, the device operation status parameters 156may correspond substantially only to the smart home device 10A. Inanother example, when the target smart home device 10 is one of thesmart home devices 10B, which is accessible by way of the smart homedevice 10A, the device operation status parameters 156 may containoperational parameter information about both the smart home device 10Aand the smart home device 10B.

The second application 148 may include voice actions. For example, auser input to the second application 148 may be an audible cue to “Set[brand(e.g.‘nest’)|thermostat|temperature] to [nn] degrees.” The secondapplication 148 may convert this into messages that ultimately becomecommands to transition the desired temperature of the thermostat 10A.

Further, an audible queue might be to “Turn on the heat.” In such ascenario, the commands provided to the thermostat 10A would set thethermostat one degree Celsius above the current ambient temperature. Ifthe thermostat 10A is in range mode, both the low and high points areraised one degree Celsius.

Additionally, an audible queue might be to “Turn on the [airconditioning|cooling|a.c.].” In such a scenario, the commands providedto the thermostat 10A would set the thermostat one degree Celsius lowerthe current ambient temperature. If the thermostat 10A is in range mode,both the low and high points are lowered one degree Celsius.

In some embodiments, an audible queue might be to “set [brand(e.g.‘nest’)|thermostat] to away.” In such a scenario, the commands providedto the thermostat 10A would change the mode of the thermostat 10A to“AWAY.” When the audible queue is “set [brand(e.g. ‘nest’)|thermostat]to home,” the commands provided to the thermostat 10A would change themode of the thermostat 10A to “HOME.”

i. Architecture

FIG. 6 illustrates a system 180 that uses an API 90 to access one ormore device services 84 to request data from, control, and/or store datathat may be useful to the smart devices (e.g., thermostat 10A, smokeand/or CO detector 10B, and/or other device 10C). As discussed above,the system 180 may be useful to enable one or more clients 182 (e.g.,third-party client and/or a principle client of the device service 84)to: provide data 184 for use in the device services 84 (e.g., to a datastore (e.g., data warehouse 185), to storage of one or more of the smartdevices, and/or to a data model of the device service 84), provide arequest 186 to control one or more of the smart devices via the deviceservice 84, and/or to receive data 188 from one or more of the smartdevices via the device service 84 (e.g., via providing a subscriptionand/or particular data query request 190), upon authorization from anauthorization server (e.g., an additional service provided by services191). As used herein, the term “client,” “application programminginterface (API) client,” and “client application” may be usedinterchangeably and may refer to an integration point for the API 90and/or device service 84. Further, it should be noted, as used herein,the terms “client device,” “third party device,” and “API client device”may be used interchangeably and refer to an electronic deviceinterfacing with the integration point (e.g., client or API client).

In embodiments where a smart thermostat 10A is present, the API 90and/or device services 84 may be used to: view a current temperature,view and/or set a target temperature, set a fan timer, view and/or settemperature modes (e.g., “heating” and/or “cooling”), view humiditydata, and/or view online status and/or last connection information. Inembodiments where a smoke and/or CO detector 10B is present, the API 90and/or device services 84 may be used to view CO and/or smoke status,view battery health of the detector 10B, view last manual test statusand/or a timestamp for the last manual test, and/or view online statusand/or last connection information. Further, in embodiments where astructure 10D (e.g., a smart home environment containing smart devices)is associated with the device service 84, the API 90 and/or deviceservices 84 may be used to: view a list of devices in the structure 10D,view energy event status (e.g., whether the structure 10D is under apreferable energy utilization period as defined by an energy utilityprogram (e.g., Rush Hour Rewards by Nest®)), view and/or set an awaystate of the structure 10D, view a postal or zip code of the structure10D, and/or set an estimated time of arrival to the structure 10. Manyother data points may be accessed and/or written to the devices via theAPI 90 and/or device services 84.

To perform these functions, the client 182 may connect to the API 90. Inone embodiment, the API 90 may include one or more hosts 192 that mayreceive and/or process the data 184 and/or the requests 186 and/or 190in near real-time and/or real-time. The hosts 192 may include a Firebasehost and/or one or more Representation State Transfer (REST) hosts 196(e.g. periodic REST and/or REST streaming transactions).

Firebase organizes data as one large JSON document. Using this scheme,the device service 84 can listen for updates (e.g., insertions,deletions, modifications) on the trees of data that the client 182 hasaccess to and/or is subscribed to, in order to synchronize these updatesbetween the clients 182 and/or the devices (e.g., 10A-10C) and/orstructures 10D.

Each data element is addressable by a Uniform Resource Locator (URL).Each data element location can store strings, numbers, Boolean valuesand/or parent/child objects or arrays. Using the API 90, a user's clientcan sync data from locations at multiple levels in the hierarchy. Forexample, an entire structure, including all devices, a single device ina structure, a group of data values (e.g., current and ambienttemperatures), and/or a single data value (e.g., battery health state).As mentioned above, these data locations may be accessed by creating aclient 182 application, using the client libraries 198 and/or usingstreaming and/or traditional REST communications.

A variety of access controls mechanisms are possible. As will bediscussed in more detail below, in some embodiments, a custom loginfeature may be used to enable the device service 84 provider to utilizecustomized authentication payloads to authorize access to the APIs 90and/or device services 84.

To provide data 184 and/or requests 186 and/or 190 to the host 192 in amanner that the API 90 may understand, an application of the client 182may be constructed to provide this data 184 and/or requests 186 and/or190. Upon authentication of access rights (which will be discussed inmore detail below), the application may utilize REST and/or clientlibraries (e.g., Firebase client libraries 198) to subscribe to datavalues via the API 90. When a subscribed data value changes, the newdata values are updated in real time and stored as a standard JSONdocument. The client 182 may then update and/or trigger an action basedupon the subscribed data. Further, when the client 182 wishes to writedata to the shared JSON document, the client 182 may provide the requestvia REST and/or Firebase. Accordingly, as mentioned above, the client182 may generate and provide the data 184 and/or requests 186 and/or 190as well as receive data 188.

The requests 186 and/or 190 and/or the data 184 are passed from the API90 to the device service 84. The device service 84 maintains a datamodel of all relevant structures 10D as well as the relevant smartdevices (e.g., thermostats 10A, detectors 10B, and/or devices 10C)associated with each of the structures 10D. The data model is generatedand updated in a subscription-based approach. For example, as newstructures 10D and/or smart devices (e.g., thermostats 10A, detectors10B, and/or devices 10C) are activated, a subscription may be registeredbetween the smart devices (e.g. 10A-10C) and/or the structure 10D andthe device service 84. Rather than require continual polling for newand/or updated data, which may result in excessive heating and/orbattery consumption of the smart devices, the subscription enables newand/or updated data provided to the device service 84 (e.g., via the API90) to be provided in near-real time, upon changes to the data modelmaintained by the device service 84.

FIG. 7 illustrates an embodiment of a process 248 for providing datarequests via the subscription-based device service 84. First, a sessionbetween the data service 84 and one or more subscribing devices (e.g.devices 10A-10C) and/or structures 10D is created (block 250). Thesession may be established for a predetermined period (e.g., 1 hour, 1day, 1 week, etc.) and may be closed at any time by either thesubscribing device and/or the device service 84.

Next, when an interaction with the system 180 occurs, a data request isreceived by the device service 84 (block 252). In one embodiment, thedata request may include a request to retrieve particular smart deviceinformation and/or a request to set particular smart device information.The request may be provided, in some embodiments, via the API 90, basedupon communications from a client 182.

Upon receiving the request, the device service may process the request(block 254). For example, the device service 84 may update itsmaintained data model based upon the request. In some embodiments, theJavaScript Object Notation (JSON) data format may be used to maintainthe device service 84's data model. One or more translation modules maytranslate non-JSON formatted data (e.g., tag-length-field (TLV)formatted data) into the JSON data format. Further details and examplesof subscription services and translation into a JSON data format andprocessing received data are described in U.S. Ser. No. 61/627,996,filed Oct. 21, 2011, entitled “User friendly, network connected learningthermostat and related systems and methods” and in U.S. Ser. No.14/508,884, filed Oct. 7, 2014, entitled “Systems and Methods forUpdating Data Across Multiple Network Architectures,” which are bothincorporated by reference herein in their entirety for all purposes.

Next, the device service 84 may wake any subscribers of the request(e.g., smart devices 10A-10C and/or structures 10D associated with therequest) (block 256). In one embodiment, the devices (e.g., thermostats10A, detectors 10B, and/or devices 10C) and/or structures 10D may beequipped with wake-on-LAN (WOL) functionality that enables a device tosleep until particular data packets are received at the WOL equippeddevice. Upon receiving these particular packets, the devices may wake,and receive data that is provided based upon the received request (block258). In some embodiments, packet filtering may be implemented on thedevices, such that only particular data packets will wake the devices,helping to ensure that the devices are only awoken when relevant data isreceived at the device 10A-10C and/or the structure 10D. Further,buffering may be used to ensure that erroneous data is not used to wakethe devices and/or structure. For example, if the client 182 sends arequest to write a new target temperature to a thermostat 10A that isone degree above the current target temperature, but then immediatelysends another request that cancels the prior request (e.g., reduces thetarget temperature down one degree), the requests may be cancelled outwithout waking the thermostat 10A (assuming both requests are receivedby the device service 84 in a buffer window prior to the thermostat 10Awake). In some embodiments, the buffer window may be 2-3 seconds.

As mentioned above, data 188 may also be provided to the client 182 fromthe smart devices (e.g., thermostat 10A, detector 10B, and/or device10C) and/or structures 10D. For example, the client 182 may displayand/or trigger actions based upon received data from the smart devicesand/or structures 10D. FIG. 8 illustrates a process 280 for providingdata from smart devices and/or structures to a client 182. As with theprocess 248 of FIG. 7, an http session is established between the deviceservice 84 and smart devices (e.g., thermostats 10A, detectors 10B,and/or devices 10C) and/or structures 10D (block 280). Upon detecting achange of relevant data in the smart devices and/or structures 10D(decision block 284), the changed data is provided to the device service84 (block 286). The device service 84 then updates the data model andprovides the updates to the client 182 (block 288). The client 182 isthen able to display the updated data and/or trigger other actions basedupon the updated data.

In one example, a client may be created to interact with a thermostat10A (e.g., using the client libraries 198). The client may be set up tomonitor two values: current temperature and target temperature. Toobtain changes to these two values, the client establishes asubscription to the thermostat object in a structure 10D. Then, when thetemperature of the thermostat 10A is adjusted, the target temperaturechanges and the device service 84 updates the data model (e.g., JSONdevice and/or structure representation), which may be synchronized withthe client 182 in near-real time. The client 182 may listen for changesand display a new target temperature and/or update the currenttemperature as it changes at the thermostat 10A.

ii. Authorization and Permissions

The API 90 and device service 84 may provide information to clients thatmay be used to build a better home experience. However, that informationis ultimately owned by the user of the smart devices (e.g., thermostats10A, detectors 10B, and/or devices 10C) and can only be shared withclients when the user explicitly allows it. Certain permissions mayenable a client to access resources in a shared data model. As such, anauthorization process may be used to enable the user to grantpermissions to clients requesting to view and/or modify data associatedwith the user's smart devices (e.g., thermostats 10A, detectors 10B,and/or devices 10C) in the data model using the authorization server191. The authorization process may use an open protocol framework (e.g.,OAuth 2.0) to allow secure authorization of third party applications toobtain limited access to an HTTP service.

The authorization server 191 may provide functionality for managing theauthorization code and access token granting processes, which will bedescribed in more detail below. There may be an authorization processfor web-based and PIN-based authorization. If a redirect universalresource identifier (URI) was entered when the client was registered,then a web-based authorization code may be in the redirected URI as acode query parameter. If a redirect URI was not entered when the clientwas registered, then a PIN-based authorization code may be displayed ina web page. PIN based authorization is generally used for devices withno web user interface, and that have an alphanumeric keypad interface.

The permissions may vary based on who the client is, the type of databeing requested, the type of access being requested, and so forth.Indeed, in some embodiments, there may be various scopes, or groups ofpredefined permissions to certain data elements, that are assigned tothe clients. Access to resources may be tied to a session (an issuedaccess token). The end user may be asked to approve granting a series ofscopes as part of the session initiation process. If the user approvesthe scopes, the permissions associated with the scopes at the time ofissue are tied to the session for the lifetime of the session, asdiscussed in detail below. Also, in some embodiments, the disclosedtechniques provide functionality to enable the client to insert theirown data into the data model using the device service 84 (e.g., via theAPI 90), retrieve their own data from data model using the deviceservice 84 (e.g., via the API 90), or to allow the client to authorizeanother third party to modify or view the client's data in the datamodel using the device service 84 (e.g., via the API 90).

FIG. 9 illustrates a flow diagram of a process 300 for a user toauthorize a client to access user data in the data model via the deviceservice 84, in accordance with an embodiment. To interact with theuser's smart devices (e.g., thermostats 10A, detectors 10B, and/ordevices 10C) by manipulating data or viewing data in the data model, theuser must first agree to let the client access user device data. Theauthorization process may begin with a link 301 to connect to the deviceservice 84 on a client site/app 302 that the user may select. Inresponse, a resource access permission page 304 and a login page 306 maybe displayed that asks the user to grant access to the client and/orsign in if not already signed into an authorization server.

The resource access permission page 304, which is described in detailbelow, may display the permission and one or more justifications for thepermission entered when the client was registered in the data model. Ifthe user accepts the permission requested for the client, anauthorization code may be returned from the authorization server to theuser, which passes the authorization code to the client, and the clientexchanges the authorization code and a client secret for an accesstoken. The client may then make API calls to the device service 84including the access token to retrieve and/or input data into the datamodel. For example, the client may request to see the currenttemperature and/or the target temperature using an API call and theaccess token which provides thermostat read permissions. As a result,the current temperature and/or the target temperature may be returned bythe device service 84 and displayed on the client site/app 308. Asshould be appreciated, any data for which the client is grantedpermissions may be accessed in the data model 307 and used as desired onthe client site/app 308. The user may revoke access at any time, whichwill inhibit the client from making any further requests for the user'ssmart devices' (e.g., thermostats 10A, detectors 10B, and/or devices10C) data.

FIG. 10 illustrates the resource access permission page 304 of FIG. 9,in accordance with an embodiment. As discussed above, this page 304 asksthe user to grant access to the client. In particular, the resourceaccess permission page 304 displays the permissions and justificationsfor the permissions when the client was registered in the data model.The justification explains what the client will do with the requesteddata and how it will benefit the user. Justifications should include theclient name, the action(s) the client can take, and the triggeringevent. For example, a sample template to write justifications includethe following:

-   -   “Allows [client name] to [take action] [because/when . . . ]”

In some embodiments, the justifications may have a minimum word length(any suitable number, such as 5, 10, 15, 20, etc.), and contain lessthan or equal to a maximum number of characters (any suitable number,such as 140, 150, 160, etc.). The user may see the justification in theresource access permission page 304 and in a permissions view within asmart device (e.g., thermostats 10A, detectors 10B, and/or devices 10C)site/app.

For example, in the illustrated embodiment, the resource accesspermission page 304 indicates that Company A would like to see dataabout the detector 10B related to smoke, carbon monoxide, and batteryinfo, and by doing so will allow certain lights to turn red during anemergency (310). Additionally, the page 304 indicates that Company Awould like to see when the user's home is set to away, which allowscertain lights to turn off when the house is set to away (312). The page304 also notifies the user that the integration may be disconnected atany time to terminate the client from using the data.

FIG. 11 illustrates a block diagram of a system 314 for authorizingclients to interact with a user's smart device (e.g., thermostats 10A,detectors 10B, and/or devices 10C) data and/or operation via the web(e.g., server to server resource requests), in accordance with anembodiment. FIG. 12 illustrates a sequence diagram 320 for authorizingclients to use a user's smart device data using the system 314 of FIG.11 via the web. As illustrated, the sequence diagram 320 depicts twelveevents occurring in a sequential order. For clarity, both FIGS. 11 and12 will be described together.

The system 314 may include a smart device user 316, a third party client318, an authorization server 191, and the device service 84 and/or API90. It should be noted that, in some embodiments, the device service 84and/or the API 90 may receive the requests for resources from the client318 and validate the access token provided by the client 318. It shouldalso be noted that, in some embodiments, the authorization server 191may provide functionality including querying client information and alist of scopes that the user granted to the client. As described indetail below, the scopes may group together one or more permissions fora specific functionality (e.g., viewing thermostat data, setting HVAC,etc.). The authorization server 191 may also authenticate the user 316and fetch the user ID, validate the user's consent to grant the client'srequested scopes, handle redirects, and receive requests for theauthorization code and the access token. In some embodiments, theauthorization server 191 may handle the requests via HTTP REST GET callswith query parameter format.

Additionally, the authorization server 191 may include one or moreservers that provide varying functionalities. For example, anauthorization server that is not exposed to the public may providefunctionality for managing the authorization codes, access tokens,client secret, scopes, and permissions, whereas a publicly exposedauthorization server may provide functionality for higher levelfunctions of the authorization code and access token granting process,such as querying client information and list of scopes requested for aclient, authenticate user and fetch user ID, validate user's consent togrant client's requested scopes, handle redirects, and receive requeststo provide access tokens for authorization codes.

The user 316, which may be a customer/owner of resources requested, maybe using a web browser in the illustrated embodiment. Event 1 322 of thesequence diagram 320 includes the user 316 sending a request to theclient 318 webpage/app that incorporates data from the data model. Inresponse, event 2 324 shows a page being returned to the user with awebpage containing a link to the authorization page. The link to theauthorization page may include the following information: response type(“code”), client ID (ID is provided to the client 318 when registered),state (a value passed from the client 318 to authorization server 191and may be used to protect against cross-site request forgery attacks).Event 3 326 may include the user 316 clicking the authorization link,thereby sending a GET request to the authorization server 191. Theauthorization server 191 responds with the resource access permissionpage 304 and the interstitial login page 306 if the user 316 is notalready logged in, as depicted in event 4 328.

Then, as indicated by event 5 330, the user 316 submits a username,password, and resource permissions to the authorization server 191. Ifthe login is successful, the authorization server 191 responds with aredirect to redirect uniform resource identifier (URI) to the user 316,as indicated by event 6 332. The redirect URI may contain the followingparameters: code (an authorization code used to obtain an access token),a state (the same value passed to the authorization server 191 earlier,which the client 318 should validate has not changed upon receipt). Theauthorization code may be a short string of alphanumeric characters withdifferent length requirements based on whether the authorization isweb-based (e.g., 14, 16, 18 characters) or PIN (6, 8, 10 characters).Also, the authorization code may be subject to expiring if not usedwithin a certain period of time based on whether the authorization isweb-based (e.g., 5, 10, 15 minutes) or PIN (e.g., 24, 48, 72 hours).Further, the authorization server 191 may create an authorization entryin the authorization tree for the user and the client that is grantedpermission in the assigned scopes. In some embodiments, once thepermission is granted, data synchronization between the API 90 and thedata service 84 may begin.

In event 7 334, the user's web browser redirects to the client 318 withthe authorization code. Upon receiving the request from the user 316containing the authorization code, the client 318 may send a POSTrequest to the authorization server 191 containing the followingparameters in event 8 336: grant type (“authorization code”), code (theauthorization code returned by the authorization server 191), client ID(the ID issued when the client was registered), and a client secret (asecret issued to the client 318 when registered).

As indicated by event 9 338, the authorization server 191 responds withan access token. The response may be an object in the JavaScript ObjectNotation (JSON) data format: \{“access_token”:“some-random-string”,“expires_at”:“time-expires ISO8601 format”}. In some embodiments, theaccess token may not expire for an extended period of time (e.g., 10,15, 20 years). Also, the access tokens may be long unique strings.

Then, as indicated by event 10 340, the client 318 requests the neededresource from the device service 84 using the API 90. The API 90 requestmay include the following parameter added: access token (the accesstoken returned in the call to the authorization server 191). That is, insome embodiments, the API client or API client device may send one ormore requests including the access token to retrieve, access, view,subscribe, or modify data elements of a data model representative of oneor more smart environments. The access token may be associated with atleast the API client or API client device and one or more scopes grantedto the API client or API client device. As previously discussed, the oneor more scopes may provide one or more access rights to one or more ofthe data elements of the data model defined by a hierarchical positionof the data elements in the data model represented by a respective pathto the data elements. It should be noted that the sending of the requestincluding the access token may be implemented as computer instructionsstored one or more tangible non-transitory computer-readable medias andexecuted by the API client or the API client device.

Sending the one or more requests with the access token enablesdownstream services (e.g., device service 84) to the API client 318 orAPI client device to use the access token to identify the one or morescopes granted to the API client or API client device. The deviceservice 84 may process the request in accordance with the granted scopesto the associated access token and API client 318 or API client device.The device service 84 responds with the requested resource in event 11342 and the client 318 includes the resource into a page included in aresponse to the user 316, as indicated by event 12 344. It should beappreciated that the client 318 may continue to make requests from thedevice service 84 to access or modify data in the data model based onthe permissions that were granted for as long as the access token isvalid. In some embodiments, the device service 84 responds with a dataobject including data objects from the data model (e.g., a metadata dataobject, a devices data object, a structures data object) based on therequest and scopes associated with the access token. Further, in someembodiments the client 318 may perform a function in addition todisplaying the returned data in a page, such as controlling a setting onthe API client device based on the data, executing a control action onthe API client device based on the data, and the like.

FIG. 13 illustrates a block diagram of a system 350 for authorizingclients to use a user's smart device (e.g., thermostats 10A, detectors10B, and/or devices 10C) data via a PIN when the devices do not have aweb UI, in accordance with an embodiment. FIG. 14 illustrates a sequencediagram 360 for authorizing clients to use a user's smart device datausing the system 350 of FIG. 13 via the PIN. For clarity, both FIGS. 13and 14 will be described at the same time.

The system 350 may include a smart device client application 352, thesmart device user 316, the authorization server 191, and the deviceservice 84 and/or API 90. It should be noted that, in some embodiments,the device service 84 and/or the API 90 may receive the requests forresources from the client application 352 and validate the access tokenprovided by the client application 352. Additionally, the authorizationserver 191 may include one or more servers that provide varyingfunctionalities. For example, an authorization server that is notexposed to the public may provide functionality for managing theauthorization codes, access tokens, client secret, scopes, andpermissions, whereas a publicly exposed authorization server may providefunctionality for higher level functions of the authorization code andaccess token granting process, such as querying client information andlist of scopes requested for a client, authenticate user and fetch userID, validate user's consent to grant client's requested scopes, handleredirects, and receive requests to provide access tokens forauthorizations codes.

The sequence of events may begin with the user 316 installing the clientapplication 352 that requires access to resources in the data model, asindicated by event 1 362 in the sequence diagram 360. In event 2 364,the client application 352 instructs the user to use a link to theauthorization server 191 including the client's name. The user 316 mayuse a web browser to enter the link and request the page to theauthorization server 191 including the client's name (event 3 366). Theauthorization server 191 responds with the resource access permissionpage 304 and the interstitial login page 306 if the user 316 is notalready logged in, as depicted in event 4 368. The user 316 then submitsapproval or denial of the resource access permissions for the clientand/or enters a username and password if login is required to theauthorization server 191 (event 5 370). In event 6 372, theauthorization server 191 responds with a result page that contains auser readable authorization code (personal identification number (PIN)).

The user may copy the PIN from the web browser and manually enter thePIN into the client application 352 (event 7 374). After the user entersthe PIN, the client application 352 submits the PIN and a client secret(provided when the client was registered) to the authorization server191, as depicted in event 8 376. Upon receipt of the PIN, theauthorization server 191 responds to the client application 352 with anaccess token (event 9 378). The client application 352 can now makeresource requests from the data model via the device service 84providing the access token as a request parameter to the API 90 and/orthe device service 84 (event 10 380). The device service 84 and/or theAPI 90 may analyze the access token and return the requested resourcesfrom the data model based on the permissions granted to the clientapplication 352 (event 11 382).

In some embodiments, the client 318 or the client application 352 mayhave their access revoked by the user at any time. For example, the usermay access a “settings” screen and revoke the permissions granted to theclient. The authorization server 191 may generate and send an accesstoken revocation message that deletes the access token assigned to theclient 318 or the client application 352. The deletion may be detectedand, if the client 318 or the client application 352 that had theiraccess deleted was the last authorized client, then data synchronizationbetween the API 90 and the data service 84 may be stopped. Further, anysessions that were authenticated with the deleted access token may bedisconnected.

In some embodiments, multi-user integration (MUI) may enable the client318 or client application 352 to open a single connection (HTTPS) andread data from multiple users. Each connection may be responsible forthe portion of the users using a particular host. Using the singleconnection may improve efficiency between server-to-server integrationsby reducing the overall number of connections. In one example, RESTstreaming may be used by clients making a call to a multiuser endpointwith a list of access tokens. In some embodiments, the response mayinclude all data for each access token, including all structures and alldevices, and metadata. The client may examine the response data to mapthe access tokens to the corresponding users and/or filter the datavalues for the information the client desires. To enable the client tomap the access tokens, a metadata section may be included in eachresponse that includes the access token associated with the data and theuser.

If the client desires to modify the list of access tokens, theconnection may be closed, the list updated, and the multi-user call maybe made by the client again to reestablish the connection. In someembodiments, when data for users associated with additional accesstokens is desired, the client may close the connection and add the addthe additional access tokens to the list to send in another request tothe multiuser endpoint. As long as the list does not exceed a thresholdnumber of access tokens, the connection will be established and datawill be returned for all of the access tokens in the list. That is, insome embodiments, the connection may not be established if more than athreshold number of access tokens are provided. It should be noted, thatsingle-client integrations (e.g., mobile apps) may typically open a newconnection for each access token and may not use MUI. To make a MUIcall, the client 318 or client application 352 may use a specificendpoint (e.g., https://developer-api.nest.com/multiplex) to make a RESTstreaming call, or the like, and include a list of access tokens in therequest. For example, the request URL may be entered as follows:

-   -   https://developer-api.nest.com/multiplex?auth=LIST_OF_ACCESS_TOKENS

The list_of_access_tokens URL parameter may be of type list and be acomma-separated list with a configured maximum number of access tokens.The authorization server 191 may validate the list against the accesstokens associated with the client 318 or the client application 352. Insome embodiments, as mentioned above, the response may include all datavalues in an all objects so the client 318 or the client application 352may filter the fields of interest and map the access tokens to thecorresponding users (e.g., by identifying the access tokens provided ina metadata section of the response and mapping them to the users).Additionally or alternatively, there may be more than one response andeach response may be particular for a single access token that was sentin the list of access tokens with the request. The metadata sectionincluding the access token provides a mechanism to identify which accesstoken with which the data and/or user is associated.

In one embodiment of multi-user integration, a method for authorizingaccess for an application programming interface (API) client or APIclient device to data of one or more data models of one or more smartdevices may include retrieving a number of access tokens from anauthorization server. The method may also include providing, via asingle connection, the plurality of access tokens in a request made bythe API client or the API client device to the API. The plurality ofaccess tokens are used to verify access rights of the API client or theAPI client device to read data for a plurality of users associated withthe one or more data models of the one or more smart devices. The methodmay be implemented as computer instructions on a tangible,non-transitory computer-readable media and executed by the API client orAPI client device.

As mentioned above, there may be one or more scopes that includespecific permissions associated with certain functionality that may begranted to application programming interface (API) clients and/or clientapplications. A scope may refer to a collection of permissions. Scopesare a unit of permission defining the ability to access or modify theuser's data. Scopes may be identified by a unique name (e.g., 64characters) and an ID number, as discussed below. Scopes enableidentifying elements in the data model by permissions to which theclient 318 has access. The elements may be located in the data modelbased on unique paths that the client 318 is granted access (e.g., read,write, read and write) via the scope granted. That is, there may be aone to one correspondence between a path in the data model and theelement to which the client 318 has access. Thus, a scope may includeproviding various access rights to a bundle of paths to elements in thedata model.

The scopes that are assigned and granted to the client 318 or the clientapplication 352 may be tied to the session (access token) for the lifeof the session. In some embodiments, the API 90 may validate that theaccess token is signed by a client secret issued by the authorizationserver 191. After validation, the API 90 may allow access to theresources in the data model according to the granted scopes associatedwith the access token using the device service 84. In some embodiments,rules may be set up that allow access to the resources if certainconditions are met. The table below shows one such rule.

Sample Rule “users” : {    “$user” : {       “.read”: “auth.for_user ==$user”,    } }

The above rule indicates that the authenticated user can read theusers/<user> element if the “for_user” field of the access token is<user>. Using this technique, rights information may be stored and usedto limit third party access to the elements for which the third partyhas granted permissions. Moreover, updates (insertions, deletions,modification) on the rights tree may be detected and any needed changesmay be made to synchronize various servers included in the system. Anauthorization tree may contain an object for each user who has grantedany client 318 or client application 352 access. Within the user objectthere may be sub-objects for every client that has been granted access.Each client object contains information on rights granted to thatclient. The below table includes an example of an authorization tree.

Authorization Tree {   auth:     {     55156: //user ID      {     1234: //client ID        {        scopes: [“thermostat read”],       granted_at ...        etc...        }      5678://client ID       {        scopes: [“thermostat read/write”, “smoke + CO read”],       granted_at ...        }      }     } }

As displayed in the table, the user with ID 55156 granted scopes to twoclients, client ID “1234” and client ID “5678”. The scope granted toclient ID “1234” includes only the thermostat read scope and the clientID “5678” includes both the “thermostat read/write” scope and the“smoke+CO read” scope. The various scopes and permissions bundled intoeach scope are discussed in detail below.

The permissions are designed and organized into scopes based on thetypes of data each client 318 might need. For example, for clients 318that only check in and get status updates, a developer may only select a“read” permission for data elements, and, as a result, only choose ascope including read permissions to the associated element paths.However, if the client 318 is designed to set device values or status,the developer may choose a “read/write” permission for those elementsand choose a scope including read/write permissions to the associatedelement paths. The scopes including the permissions that are selectedfor a particular client should match the client's features. As theclient's features expand, the client 318 may need new permissions. Insome embodiments, a new client version may be created with a scope thatincludes the newly required permissions and that client version may beoffered to the users 316. It should be understood that if the client 318is authorized the assigned scope, then the client may receive all of thepermissions defined for that scope. Also, if multiple scopes areauthorized for a client 318, then the client may receive a superset ofall permissions combined contained in those scopes. Below is a table ofsome general scopes and the permissions that each scope includes,according to an embodiment.

Scopes and Permissions Scope: Thermostat read Grants read permission tomost of the Thermostat and Structure data values Scope: Thermostatread/write Grants read permission to all of the Thermostat data valuesGrants write permission to these Thermostat data values:fan_timer_active, all target_temperature_x fields and hvac_mode Grantsread permission to most of the Structure data values Scope: Smoke + COread Grants read permission to all the Smoke + CO Alarm data values andmost of the Structure data values Scope: Away read Grants readpermission to most of the Structure data values Scope: Away read/writeGrants read permission to most of the Structure data values Grantsread/write permission for away Scope: ETA write Grants read permissionto most of the Structure data values Grants write permission to etaScope: Postal code read Grants read permission for postal_code Scope:Product data read/write Grants read permissions for all of the Companydata values Grants read/write permissions to software version and all ofthe resource use data values

To illustrate, if a developer is registering a client 318 that listensto (e.g., reads) the ambient temperature, target temperature and theaway state of the home, then the developer would choose the “thermostatread” scope, which provides only read access to those data elements.Conversely, a client 318 that needs to actively modify targettemperature, heat/cool mode or fan timer should be assigned the“thermostat read/write” scope, which would provide write access to thosedata elements, and retain read access to the other thermostat andstructure data elements. Another client 318 might track smoke and COstate, so the “smoke+CO alarm read” scope may be chosen to provide readpermissions to those data elements. Still another client 318 could focussolely on the home, and take action when the user 316 arrives home, orafter the user leaves the home. In such a case, the “away read/write andETA write” scope may be chosen.

The below tables illustrate the various scopes for element paths in thedata model for smart devices, such as thermostats 10A and detectors 10B,and a structure in more detail. The names of the scopes are across thetop row of the table, the second row includes the scope ID, the thirdrow includes a version number of the scope, and the leftmost columnincludes the field/data element paths. In some embodiments, a permissionfield in the data model may store all the permissions included for theselected scope(s). When the user 316 approves the requested scope forthe client 318, an authorization session may be created and the stringincluding all permissions for the client 318 may be copied into a rowwhere authorization session information resides including the accesstoken. The approved scopes for the client may be stored as part of alogin string in the data model where the access token is stored. Theaccess token is reused each time the client requests data from the dataservice 84. It should be noted, that in some embodiments, every scopehas at least read permissions to an access_token and client_versionelement included in a “Metadata” object of the data model.

Thermostat Read Scope Thermostat Thermostat Name read read Fields ID 1019 Version  1  2 /devices/thermostats/device_id/device_id READ READ/devices/thermostats/device_id/local READ READ/devices/thermostats/device_id/software_version READ READ/devices/thermostats/device_id/structure_id READ READ/devices/thermostats/device_id/name READ READ/devices/thermostats/device_id/name_long READ READ/devices/thermostats/device_id/last_connection READ READ/devices/thermostats/device_id/is_online READ READ/devices/thermostats/device_id/can_cool READ READ/devices/thermostats/device_id/can_heat READ READ/devices/thermostats/device_id/is_using_emergency_heat/devices/thermostats/device_id/has_fan READ READ/devices/thermostats/device_id/fan_timer_active READ READ/devices/thermostats/device_id/fan_timer_timeout READ READ/devices/thermostats/device_id/has_leaf READ READ/devices/thermostats/device_id/temperature_scale READ READ/devices/thermostats/device_id/target_temperature_f READ READ/devices/thermostats/device_id/target_temperature_c READ READ/devices/thermostats/device_id/target_temperature_high_f READ READ/devices/thermostats/device_id/target_temperature_high_c READ READ/devices/thermostats/device_id/target_temperature_low_f READ READ/devices/thermostats/device_id/target_temperature_low_c READ READ/devices/thermostats/device_id/away_temperature_high_f READ READ/devices/thermostats/device_id/away_temperature_high_c READ READ/devices/thermostats/device_id/away_temperature_low_f READ READ/devices/thermostats/device_id/away_temperature_low_c READ READ/devices/thermostats/device_id/hvac_mode READ READ/devices/thermostats/device_id/ambient_temperature_f READ READ/devices/thermostats/device_id/ambient_temperature_c READ READ/devices/thermostats/device_id/humidity READ/structures/structure_id/structure_id READ READ/structures/structure_id/thermostats READ READ/structures/structure_id/smoke_co_alarms READ READ/structures/structure_id/away READ READ /structures/structure_id/nameREAD READ /structures/structure_id/country_code READ READ/structures/structure_id/postal_code/structures/structure_id/peak_period_start_time READ READ/structures/structure_id/peak_period_end_time READ READ/structures/structure_id/time_zone READ READ/structures/structure_id/eta /structures/structure_id/data_upload

As described above and shown in the Themostat Read Scope table, thethermostat read scope grants read permission to most of the thermostatand structure data values in the data model. Version 1 of the thermostatread scope does not provide read access to the humidity data valuesbecause the element may have been added to the data model after version1 was created. As depicted, version 2 of the thermostat read scopegrants read permission to the humidity data path in addition to all ofthe other elements included in version 1.

Thermostat Read/Write Scope Thermostat Thermostat Name read/writeread/write Fields ID 11 20 Version  1  2/devices/thermostats/device_id/device_id READ READ/devices/thermostats/device_id/local READ READ/devices/thermostats/device_id/software_version READ READ/devices/thermostats/device_id/structure_id READ READ/devices/thermostats/device_id/name READ READ/devices/thermostats/device_id/name_long READ READ/devices/thermostats/device_id/last_connection READ READ/devices/thermostats/device_id/is_online READ READ/devices/thermostats/device_id/can_cool READ READ/devices/thermostats/device_id/can_heat READ READ/devices/thermostats/device_id/is_using_emergency_heat READ READ/devices/thermostats/device_id/has_fan READ READ/devices/thermostats/device_id/fan_timer_active READ READ WRITE WRITE/devices/thermostats/device_id/fan_timer_timeout READ READ/devices/thermostats/device_id/has_leaf READ READ/devices/thermostats/device_id/temperature_scale READ READ/devices/thermostats/device_id/target_temperature_f READ READ WRITEWRITE /devices/thermostats/device_id/target_temperature_c READ READWRITE WRITE /devices/thermostats/device_id/target_temperature_high_fREAD READ WRITE WRITE/devices/thermostats/device_id/target_temperature_high_c READ READ WRITEWRITE /devices/thermostats/device_id/target_temperature_low_f READ READWRITE WRITE /devices/thermostats/device_id/target_temperature_low_c READREAD WRITE WRITE /devices/thermostats/device_id/away_temperature_high_fREAD READ /devices/thermostats/device_id/away_temperature_high_c READREAD /devices/thermostats/device_id/away_temperature_low_f READ READ/devices/thermostats/device_id/away_temperature_low_c READ READ/devices/thermostats/device_id/hvac_mode READ READ WRITE WRITE/devices/thermostats/device_id/ambient_temperature_f READ READ/devices/thermostats/device_id/ambient_temperature_c READ READ/devices/thermostats/device_id/humidity READ/structures/structure_id/structure_id READ READ/structures/structure_id/thermostats READ READ/structures/structure_id/smoke_co_alarms READ READ/structures/structure_id/away READ READ /structures/structure_id/nameREAD READ /structures/structure_id/country_code READ READ/structures/structure_id/postal_code/structures/structure_id/peak_period_start_time READ READ/structures/structure_id/peak_period_end_time READ READ/structures/structure_id/time_zone READ READ/structures/structure_id/eta /structures/structure_id/data_upload

As described above and shown in the Themostat Read/Write Scope table,the thermostat read/write scope grants read permission to all of thethermostat data values, grants write permission to fan_timer_active, alltarget_temperature_x fields and hvac_mode data elements, and grants readpermission to most of the structure data values. It should be notedthat, in some embodiments, certain authorization rules may ensure thatwhen data is written (e.g., modified) by a third party, the modifieddata includes a field (e.g., “touched_by”) that is set equal to areserved value indicating that a third party made a change and/or amodified at date/time that is set to date/time the data was modified. Inthis way, third party activity with resources in the data model may belogged and monitored.

Smoke + CO Read Scope Smoke + Smoke + Name CO read CO read Fields ID 1221 Version  1  2 /devices/smoke_co_alarms/device_id/device_id READ READ/devices/smoke_co_alarms/device_id/locale_(—) READ READ/devices/smoke_co_alarms/device_id/software_version READ READ/devices/smoke_co_alarms/device_id structure_id READ READ/devices/smoke_co_alarms/device_id/name READ READ/devices/smoke_co_alarms/device_id/name_long READ READ/devices/smoke_co_alarms/device_id/last_connection READ READ/devices/smoke_co_alarms/device_id/is_online READ READ/devices/smoke_co_alarms/device_id/battery_health READ READ/devices/smoke_co_alarms/device_id/co_alarm_state READ READ/devices/smoke_co_alarms/device_id/smoke_alarm_state READ READ/devices/smoke_co_alarms/device_id/ui_color_state READ READ/devices/smoke_co_alarms/device_id/is_manual_test_active READ/devices/smoke_co_alarms/device_id/last_manual_test_time READ/structures/structure_id/structure_id READ READ/structures/structure_id/thermostats READ READ/structures/structure_id/smoke_co_alarms READ READ/structures/structure_id/away READ READ /structures/structure_id/nameREAD READ /structures/structure_id/country_code READ READ/structures/structure_id/postal_code/structures/structure_id/peak_period_start_time/structures/structure_id/peak_period_end_time/structures/structure_id/time_zone READ READ/structures/structure_id/eta /structures/structure_id/data_upload

The smoke+CO read scope grants read permission to all the smoke+CO alarmdata values and most of the structure data values, as show in the tableabove. The smoke+CO read scope version 2 includes the same permissionsfor all of the data values included in version 1 but adds additionalread permission to the is_manual_test_active data element and thelast_manual_test_time data element. The name data value may be displayedin user interface labels, while the name_long may be used in long formtext. Device_id may be a string that uniquely represents this device.When a device is connected to multiple clients, each developer may see adifferent device_id for that device. In embodiments where the samedeveloper has installed multiple clients for the device, the developermay see the same device_id. The locale data value may include thelanguage and country code assigned to the device. Software_version mayinclude a string that represents the firmware currently installed on thedevice. Structure_id may include a string that uniquely represents thisstructure (the structure that the device is paired with).Last_connection may include the timestamp of the last successfulconnection to the data service 84. Is_online may include the onlinestatus that is determined by using the last_connection time and anexpected reconnection window that is device specific. Battery_health mayinclude a string that states whether the battery is OK or whether itneeds to be replaced.

Co_alarm_state may include values that increase in severity. Forexample, when the CO levels are rising, the co_alarm_state may show“warning” and when the user should exit the home, the co_alarm_state mayshow “emergency.” Smoke alarm state may include values that increase inseverity. For example, when the smoke levels are rising, thesmoke_alarm_state may show “warning” and when the user should exit thehome, the smoke_alarm_state may show “emergency.” Theis_manual_test_active data value is normally “false” but may be “true”when a smoke or CO test is started. Last_manual_test_time may includethe timestamp of the last successful manual smoke or CO test. Theui_color_state data value may be derived from is_online, battery_health,co_alarm_state, and smoke_alarm_state. The ui_color_state may mirror thecolor that is displayed on an app and/or the device.

Away Read Scope Away Name read Fields ID 14 Version  1/structures/structure_id/structure_id READ/structures/structure_id/thermostats READ/structures/structure_id/smoke_co_alarms READ/structures/structure_id/away READ /structures/structure_id/name READ/structures/structure_id/country_code READ/structures/structure_id/postal_code/structures/structure_id/peak_period_start_time/structures/structure_id/peak_period_end_time/structures/structure_id/time_zone READ /structures/structure_id/eta/structures/structure_id/data_upload

As described above and shown in the Away Read Scope table, the away readscope grants read permission to most of the structure data values. Forexample, version 1 of the away read scope grants read permission to/structures/structure_id/structure_id,/structures/structure_id/thermostats,/structures/structure_id/smoke_co_alarms, /structures/structure_id/away,/structures/structure_id/name, /structures/structure_id/country_code,and /structures/structure_id/time_zone. Version 1 of the away read scopedoes not provide read or write permission to the following dataelements: /structures/structure_id/postal_code,/structures/structure_id/peak_period_start_time,/structures/structure_id/peak_period_end_time,/structures/structure_id/eta, or /structures/structure_id/data_upload.It should be noted that the away field may indicate whether thestructure is occupied and may include three states: home (someone is inthe house, either because the smart device determines that someone is inthe house based on motion sensor data or the user has explicitly set thestructure to home via an application, the client, or ETA), away (theuser has explicitly set the structure to away), auto-away (the smartdevice has determined that no one is in the structure).

Away Read/Write Scope Away Name read/write Fields ID 15 Version  1/structures/structure_id/structure_id READ/structures/structure_id/thermostats READ/structures/structure_id/smoke_co_alarms READ/structures/structure_id/away READ WRITE /structures/structure_id/nameREAD /structures/structure_id/country_code READ/structures/structure_id/postal_code/structures/structure_id/peak_period_start_time/structures/structure_id/peak_period_end_time/structures/structure_id/time_zone READ /structures/structure_id/eta/structures/structure_id/data_upload

As described above and shown in the Away Read/Write Scope table, theaway read/write scope grants read permission to most of the structuredata values (e.g., the same data values that read permissions aregranted in the away read scope) and grants read/write permission for theaway data value.

ETA Write Scope Name ETA write Fields ID 17 Version  1/structures/structure_id/structure_id READ/structures/structure_id/thermostats READ/structures/structure_id/smoke_co_alarms READ/structures/structure_id/away /structures/structure_id/name READ/structures/structure_id/country_code READ/structures/structure_id/postal_code/structures/structure_id/peak_period_start_time/structures/structure_id/peak_period_end_time/structures/structure_id/time_zone READ /structures/structure_id/etaWRITE /structures/structure_id/data_upload

As described above and shown in the ETA Write Scope table, the ETA writescope grants read permission to most of the structure data values andgrants write permission to the eta data value. For example, version 1 ofthe ETA write scope grants read permission to/structures/structure_id/structure_id,/structures/structure_id/thermostats,/structures/structure_id/smoke_co_alarms, /structures/structure_id/name,/structures/structure_id/country_code, and/structures/structure_id/time_zone. Version 1 of the away read scopedoes not provide read or write permission to the following dataelements: /structures/structure_id/away,/structures/structure_id/postal_code,/structures/structure_id/peak_period_start_time,/structures/structure_id/peak_period_end_time,/structures/structure_id/eta, or /structures/structure_id/data_upload.It should be noted that ETA is an object, set on a structure and onlywrite access is allowed. The ETA field should be used to provideinformation on when the smart thermostat 46 should prepare thetemperature of a house for people arriving.

Postal Code Read Scope Postal code Name read Fields ID 22 Version  1/structures/structure_id/postal_code READ

As described above and shown in the Postal Code Read Scope table, thepostal code read scope grants read permission to the postal code datavalue.

Product Data Read/Write Scope Product data Name read/write Fields ID 23Version  1/devices/$company/$product_type/product_id/identification/device_id READ/devices/$company/$product_type/product_id/identification/serial_numberREAD /devices/$company/$product_type/product_id/location/structure_idREAD /devices/$company/$product_type/product_id/software/versionREAD/WRITE/devices/$company/$product_type/product_id/resource_use/electricity/valueREAD/WRITE/devices/$company/$product_type/product_id/resource_use/electricity/measurement_reset_timeREAD/WRITE/devices/$company/$product_type/product_id/resource_use/electricity/measurement_timeREAD/WRITE/devices/$company/$product_type/product_id/resource_use/gas/valueREAD/WRITE/devices/$company/$product_type/product_id/resource_use/gas/measurement_reset_timeREAD/WRITE/devices/$company/$product_type/product_id/resource_use/gas/measurement_timeREAD/WRITE/devices/$company/$product_type/product_id/resource_use/water/valueREAD/WRITE/devices/$company/$product_type/product_id/resource_use/water/measurement_reset_timeREAD/WRITE/devices/$company/$product_type/product_id/resource_use/water/measurement_timeREAD/WRITE /structures/structure_id/devices/$company/$product_type READ

As described above and shown in the Product Data Read/Write Scope table,the product data read/write scope grants read permission to some of thecompany and structures data values and grants read/write permission tomost of the company data values. For example, version 1 of the productdata read/write scope grants read permission to/devices/$company/$product_type/product_id/identification/device_id,/devices/$company/$product_type/product_id/identification/serial_number,/devices/$company/$product_type/product_id/location/structure_id, and/structures/structure_id/devices/$company/$product_type. Further, theproduct data read/write scope provides read/write permissions to/devices/$company/$product_type/product_id/software/version,/devices/$company/$product_type/product_id/resource_use/electricity/value,/devices/$company/$product_type/product_id/resource_use/electricity/measurement_reset_time,/devices/$company/$product_type/product_id/resource_use/electricity/measurement_time,/devices/$company/$product_type/product_id/resource_use/gas/value,/devices/$company/$product_type/product_id/resource_use/gas/measurement_reset_time,/devices/$company/$product_type/product_id/resource_use/gas/measurement_time,/devices/$company/$product_type/product_id/resource_use/water/value, and/devices/$company/$product_type/product_id/resource_use/water/measurement_reset_time.

To assign scopes to clients 318 and/or client applications 352, adeveloper may first need to register the client 318 and/clientapplication 352 in the data model. Developers may need a developeraccount to be eligible to create clients. Developer accounts may becreated by users and the users may only be allowed one developeraccount. When initially created, the developer account may have lowprovisioning limits. Provisioning limits define how many clients adeveloper may have associated with it, and how many unique users aclient may have. Each client may have its own user limit. User limitsmay be defined as soft and hard. Soft limits may be exposed to thedeveloper and hard limits may be enforced programmatically. In someembodiments, a client active flag may (e.g., Boolean) may be set thatindicates if the client is active. If the client active flag is false,no new sessions may be authorized and no access tokens can be validated.Also, a developer active flag (e.g., Boolean) may indicate if thedeveloper is active. If the developer active flag is false, no newclients may be created, but existing clients may continue to work,including initiating new sessions.

The authorization server 191 may collect various statistics duringoperation. For example, the authorization server 191 may collectstatistics related to authorizations, created access tokens requests,successful created access tokens requests, failed created access tokensrequests, access token validation requests, successful access tokenvalidation requests, failed access token validation requests, accesstokens by user requests, deleted access tokens requests, successfuldeleted access tokens requests, failed deleted access tokens requests,created client secrets requests, retrieved client secret requests,successful retrieved client secret requests, failed retrieved clientsecret requests, deleted client secret requests, successful deletedclient secret requests, failed deleted client secret requests, and/orreserved client sessions.

When creating a client, the developer may select the scopes that theclient may need based on their intended use of the data andfunctionality. It should be noted that the term client may refer to adeveloper created integration point which defines the set of scopes anend user will be asked to grant the developer. It should also be notedthat the term vendor may refer to an organization that produces thirdparty devices (e.g., an electronic device produced by a manufacturerthat does not host the data model) in a service or data streams. Thedata model may include two tables to store vendor data (vendors table)and associations with developers (vendor developer association table).The vendors table may contain the following fields at a minimum: uniqueID (a UUID), data path name, and created at timestamp. The UUID isassigned when the vendor record is created. The UUID value may not bechanged after creation. The data path name may include a unique string,with no spaces, that may be used to identify the vendor's section of thedata model. The data path name is not intended to be exposed to endusers. The value of the data path name may not be changed after it iscreated. The created at timestamp may include the timestamp of when thevendor was created.

The vendor developer association table may map the vendors to thedevelopers that created the vendors in the data model. The vendordeveloper association table may include at least three columns: vendorID, developer ID, and created at timestamp. The vendor ID may includethe ID of the vendor, which may be a foreign key to the vendors table.The developer ID may include the ID of the developer, which may be aforeign key to the developers table. The created at timestamp mayinclude the timestamp of when the vendor developer association wascreated. In some embodiments, there may be a one to one relationshipbetween a developer and a vendor. That is, there may be a programmaticrestriction that only allows one developer to have one vendor.

APIs may be used to manage the vendors and the vendor developerassociations. For example, functionality provided by the APIs mayinclude creating a vendor, associating a vendor with a developer(associating a vendor with a developer may add the developer's user tothe vendor user group), and disassociating a vendor from a developer(disassociating a vendor from a developer may inhibit new clients beingcreated with the vendor data scopes but may not remove vendor datascopes and permissions from existing clients and authorizationsessions).

In some embodiments, an assignable permission may be used by the scopes.An assignable permission may include an attribute placeholder in certainelement data paths that will be replaced with the vendor data path nameswhen clients 318 are created by the developer. For example, a generaldefinition of an assignable permission may include /$vendor/* and/structures/*/$vendor/clients/*. The assignable permission after beingassigned to a client for a vendor named “Company A” may include/companya/* and /structures/*/companya/clients/*. If a scope isassignable, a replacement may be run on all placeholders when the scopeis added to the client 318. In some embodiments, scopes with assignableattributes may be restricted to developers who are in the vendor usergroup.

The assignable permissions and associated vendors may enable a developerto have a vendor associated with it and the string to access the dataelement. The assignable permission allows a vendor to provide itsspecific data into the data model and to read that data as desired usingtheir vendor specific data path. As such, the data model may include asection with vendor's device id and data specific to the client to beentered into the model. The assignable permission offers selectivevisibility into the data model based on vendor. Each device added gets anew device id and permissions levels to allow access to certain data.Each vendor may only be allowed to see data specific to each respectivevendor. To enable a client to enter and read data related to theirdevices into the data model, a vendor record may be created in thevendors table and a record may be created that associates the vendor tothe developer in the vendor developer association table. The vendor canthen register specific devices (the vendor has a device of a device typeto associate with a structure, so a record is created for that device ina user's structure in the data model) and use device services 84 toaccess the data model including the vendor specific data (using datapath name with the vendor's name inserted via the assignablepermissions). In some embodiments, a first vendor specific informationin the data model may be accessed by one or more other vendors if thefirst vendor authorizes the one or more other vendors.

In some embodiments, a client 318 may be locked with the scopes that areprovided by the developer when creating the client 318. If new elementsare added to the data model and included in different versions ofcertain scopes, a new client may be created and assigned the scopesincluding the new elements. In some embodiments, updatable client scopesmay be used to version the client. If it is desirable to change thescope information for a client, a different version of the clientincluding the desired scopes may be selected. For example, version 1 ofthe client may be assigned scope with ID “10” and version 2 of theclient may be assigned scopes with IDs “10” and “20”. A message mayappear in an end user app that indicates a developer has updated theirclient and would like to have access to the following permissions. Ifthe user 316 approves, then the permissions for version 2 are copiedinto the permissions list for the authorization session and included inthe string including the access token without having to go through aback and forth process between the device service 84 and/or API 90 andthe client 318. The process may include one click by the user to changean existing session for a client 318 to modify the allowed scopes.

In some embodiments, various database tables may be used to managevendors, developers, clients, access tokens, and the like. The tablesmay be designed in a relational manner. That is, some of the tables mayshare elements that are the same to match the elements and pull all ofthe information related to those particular elements. For example, aclient table may include a client ID and a user table may include a userID. An access token table may include an access token ID data elementand the client ID and the user ID data elements. In doing so, the accesstoken table shows which client ID's and user ID's are associated withwhich access token ID's. Similarly, an authorization code table mayinclude an authorization code ID data element and both the user ID andthe client ID. In doing so, the authorization code table shows whichclient ID's and user ID's are associated with which authorization codeID's. In addition, a scopes table may be used to maintain a scope ID andthe permissions included in the scopes. When the user approves a scopefor a client, the scope ID that is approved and the access token ID thatcorrelates to the client may be stored in an access token and scopestable, and so forth.

In some embodiments, the authorization server 191 may include one ormore servers that provide different functionality. For example, oneserver may not be exposed to the public and include low level functionsfor managing authorization codes, access tokens, client secrets, scopesand permissions, while a second server may be exposed to the public andinclude functions for higher level logic of the authorization code andaccess token granting process (query client information and list ofscopes assigned, authenticate user and fetch user ID, validate user'sconsent to grant client's requested scopes, handle redirects, receiverequest for authorization code and access token in a GET REST webservice call with query parameter format).

The internally-facing server (e.g., the server that is not publiclyexposed) may include multiple API URLs that provide variousfunctionalities. For example, the functionalities may include creatingnew authorization codes, creating new access tokens, validating accesstokens, deleting access tokens, creating new client secrets, retrievingclient ID, deleting client secrets, and the like. The requests andresponses may be in the form of JSON.

In some embodiments, an API URL to retrieve an authorization code may beused. A request to the API URL may include the user ID, client ID, PINrequest, permissions, and/or associated scope IDs. The response mayreturn a status, the authorization code, expires at date/time, and/orthe scope IDs.

In some embodiments, an API URL to retrieve an access token may be used.A request to the API URL may include the client ID, client secret,and/or authorization code. The response may return a status, the accesstoken, and/or expires at date/time.

In some embodiments, an API URL to validate an access token may be used.A request to the API URL may include the access token, which may be along unique string. In some embodiments, the access token may include aleading letter, “c”, a dot “.”, and a long random string where thecharacters are all URL compatible (e.g.,c.hpNS6bLYNOqYzhAyAIR200dzR6asdfswerASDFAFS324235). The response mayreturn a status, the user ID, the client ID, the user token,permissions, and the scope IDs if the access token is valid.

In some embodiments, an API URL to delete an access token may be used.If the deletion is successful, a response may include the access token,expires at date/time, created at date/time, ID, and client ID. If thedeletion fails, the response may include a status indicating the same.

In some embodiments, an API URL to create a client secret and/or replacean existing client secret for a client ID may be used. A response mayinclude the client ID and the client secret that is created.

In some embodiments, an API URL to get the client secret may be used. Aresponse may include the client secret that is requested.

In some embodiments, an API URL to get a client ID and a client secretmay be used. A response may include the client ID and the client secretthat is requested.

In some embodiments, an API URL to delete a client secret may be used.If a deletion request is successful, the response may include a statusindicating that the deletion was successful. If the deletion requestfailed, then the response may include a status indicating that thedeletion failed.

The publicly exposed server used by the authorization server 191 mayalso provide various functionality, such as validating an access token,getting an authorization code, revoking access to a user's data for aclient, removing authorizations for all user's clients, getting allclients for a user, getting a specific client or a user with sessions,getting all clients, checking if a client exists, getting a client ID,updating a client, deleting a client, creating a client, setting theactive state on a client, setting the users limit on a client, gettingthe status of a client's users limit, getting developer information,updating a developer, creating a new developer account, setting theactive state on a developer, setting the clients limit on a developer,setting the support flags on a developer, updating a justification for ascope, getting all clients for a developer, getting client for aspecific developer, getting all client categories, getting all scopes,getting all restrictions on a scope, adding a restriction to a scope,removing a restriction from a scope, obtaining an access token using anauthorization code, populating target structure with a fake device(thermostat), and/or deleting a session. The functionalities may beincluded in various API URLs, as generally described below.

In some embodiments, an API URL that validates an access token may beused. A request to the API URL may include the access token. If theaccess token is not valid, only a valid field may be returned indicatingthat the access token is not valid. If the access token is valid, thenthe valid field, user ID, client ID, company name, client name, usertoken, permissions, session ID, and/or scope IDs may be returned.

In some embodiments, an API URL to get an authorization code may beused. A request may include a client ID. If successful, the response mayinclude a status and the authorization code, expires at date/time, andscope IDs.

In some embodiments, an API URL to revoke access to user's data for aclient may be used. A request to the API URL may include an access tokenassociated with a client and user. If revocation is successful, theresponse may include a status and a message indicating that the sessionhas been deleted. If revocation is unsuccessful, an error response maybe returned and include a reason for the error, such as the session wasnot found or was unable to be deleted.

In some embodiments, an API URL to remove authorizations for all user'sclients may be used. A request to the API URL may include an accesstoken. If removal is successful, the response may include a status and amessage indicating that the session has been deleted. If removal isunsuccessful, an error response may be returned and include a messageindicating that the session was unable to be deleted.

In some embodiments, an API URL to get all clients for a user (includingsessions) may be used. A request to the API URL may include an accesstoken associated with the clients and the user. A response may includean ID, name, company name, description, redirect URI, scopes (ID,justification, name, version), targeted number users, intended usage,active, active, users limit, visibility IDs, category IDs, sessions,modified at date/time, created at date/time, and so forth.

In some embodiments, an API URL to get a specific client for a user withsessions may be used. A request may include an access token associatedwith the client and the user. A response may include information relatedto the client, such as an ID, name, company name, description, redirectURI, scopes (ID, justification, name, version), targeted number users,intended usage, active, active, users limit, visibility IDs, categoryIDs, sessions, modified at date/time, created at date/time, and soforth.

In some embodiments, an API URL to get all clients may be used. Aresponse may include client information, such as ID, name, company name,description, redirect URI, support URL, scopes (ID, justification, name,version), targeted number users, intended usage, active, active, userslimit, visibility IDs, category IDs, sessions, modified at date/time,created at date/time, and so forth.

In some embodiments, an API URL to check if a client exists may be used.A request may include an access token and parameters including a name(e.g., URL encoded name to check). A response may include a status,name, in use field, and so forth.

In some embodiments, an API URL to update a client may be used. Arequest may include an access token and fields related to the client toupdate, such as name, description, redirect URI, support URL, targetednumber users, and/or intended usage. It should be noted that all fieldsmay be optional and only the fields included in the request may beupdated. The response may include a status and all fields related to theclient, such as ID, name, company name, description, redirect URI,support URL, scopes (ID, justification, name, version), targeted numberusers, intended usage, active, users limit, visibility IDs, categoryIDs, developer IDs, modified at date/time, created at date/time, and soforth.

In some embodiments, an API URL to delete a client may be used. Arequest may include an access token associated with the client todelete. A response may include a status indicative of whether thedeletion request was successful. In some embodiments, a client may bedeleted if it has fewer than a threshold number of users (e.g., 25, 30,35) to which it is associated. For example, in some embodiments, theowner may delete clients that have less than 25 users.

In some embodiments, an API URL to create a client may be used. Arequest may include an access token and fields including developer ID,name, description, redirect URI, support URL, targeted number users,intended usage, scopes (ID, justification), and/or category IDs. In someembodiments, the name may be unique. A response may include a status andfields including ID, name, company name, description, redirect URI,support URL, scopes (ID, justification, name, version), targeted numberusers, intended usage, active, visibility IDs, category IDs, developerID, secret, modified at time/date, and/or created at time/date. An errorresponse may be returned in several instances, including when there isno developer account, the provisioning limit is exceeded, the user doesnot own the developer account, the developer is not active, there is aduplicate client name, the requestor is unauthorized, and/or therequestor is not a staff user.

In some embodiments, an API URL to set active state on a client may beused. A request may include an access token and an active state. Aresponse may include a status and the active state.

In some embodiments, an API URL to set the users limit on a client maybe used. A request may include an access token and a soft and a hardnumber of users limit. A response may include a status and the soft andhard limits.

In some embodiments, an API URL to get the status of a client's userlimit may be used. A request may include an access token. A response mayinclude a status, user limit, user count, and/or status OK (e.g., set to“true” if the users limit is not exceeded and set to “false” if overusers limit).

In some embodiments, an API URL to get developer information may beused. A request may include an access token. A response may include astatus and developer information, such as ID, user ID associated withthe developer, active state, client limit, address information, name,phone, company name, company URL, industry, company size, support(commercial and paid), modified at time/date, and/or created attime/date.

In some embodiments, an API URL to update a developer may be used. Arequest may include an access token and developer information to update,such as phone, company name, address information, company URL, industry,and/or company size. It should be noted that, in some embodiments, allfields in the body of the request may be optional and only the submittedfields may be updated. A response may include a status and thedeveloper's information, such as ID, user ID, active, client limit,address information, name, phone, company name, company URL, industry,company size, support (commercial and paid), modified at time/date,and/or created at time/date.

In some embodiments, an API URL to create a developer account may beused. A request may include an access token and developer information,such as user ID, name, phone, company name, address information (e.g.,first street information, second street information, city, state, postalcode, country), company URL, industry, and/or company size. A responsemay include a status and the developer's information, such as ID, userID, active, client limit, address information (e.g., first streetinformation, second street information, city, state, postal code,country), name, phone, company name, company URL, industry, companysize, support (commercial and paid), modified at time/date, and/orcreated at time/date.

In some embodiments, an API URL to set the active state on a developermay be used. A request may include an access token and active state of adeveloper. A response may include a status and the active state of thedeveloper.

In some embodiments, an API URL to update a scope's justification may beused. A request may include an access token, scope ID, and updatedjustification. The response may include a status, scope ID, and updatedjustification.

In some embodiments, an API URL to get all clients for a developer maybe used. A request may include an access token. A response may includeclient information, such as client ID, name, company name, description,redirect URI, support URL, scopes (ID, justification, name, version),targeted number users, intended usage, active, users limit, visibilityIDs, category IDs, secret, modified at date/time, and/or created atdate/time.

In some embodiments, an API URL to get all client for a specificdeveloper may be used. A request may include an access token. A responsemay include a status and client information, such as client ID, name,company name, description, redirect URI, support URL, scopes (ID,justification, name, version), targeted number users, intended usage,active, users limit, visibility IDs, category IDs, developer ID, secret,modified at date/time, and/or created at date/time.

In some embodiments, an API URL to get all client categories may beused. A response may include a status, client category ID, and name forthe client category.

In some embodiments, an API URL to get all scopes may be used. Aresponse may include a status, scope ID, scope name, and version of thescopes.

In some embodiments, an API URL to get all restrictions on a scope maybe used. Restrictions may limit a scope to particular data elements,clients, users, and so forth. A response returned by this API URL mayinclude a status and names of user groups restricting the scope.

In some embodiments, an API URL to add a restriction to a scope may beused. A request may include the restriction to be added to the scope andscope ID. A response may include a status and a message field indicatingthat the scope restriction has been added.

In some embodiments, an API URL to delete a restriction to a scope maybe used. A request may include the restriction to be deleted and scopeID. A response may include a status and a message field indicating thatthe scope restriction has been deleted.

Server to Server Call from Client to Authorization Server to Obtain anAccess Token from an Authorization Code API URL POST/oauth2/access_token?code=STRING&client_id=STRING&client_secret=STRING&grant_type=authorization_code Request:   url parameters:    ∘ code :the authorization_code provided in the call to /oauth2/authorize.    ∘client_id : id of the client (application) requesting access to a user'sdata.    ∘ client_secret : secret key provided by Nest to client. Thisis also       sometimes called a “application key”.    ∘ grant_type :may be authorization_code Response:   status: 200   content type :application/json   body :      {      “access_token”:“STRING”,     “expires_in”:LONG // number of seconds until token expires      }Error Response:   Missing parameter:    ∘ status: 400    ∘ contenttype:application/json    ∘ body: {“error”:“missing_paramenter”,“error_description”:“missing       required parameters: PARM_NAME”}  Authorization code not found:    ∘ status: 400    ∘ contenttype:application/json    ∘ body: {“error”:“oauth2_error”,“error_description”:“authorization code not       found”}  Authorization code expired:    ∘ status: 400    ∘ contenttype:application/json    ∘ body: {“error”:“oauth2_error”,“error_description”:“authorization code       expired”}   Client secretnot found:    ∘ status: 400    ∘ contenttype: application/json    ∘body: {“error”:“oauth2_error”, “error_description”:“client secret not      found”}   Client is not active:    ∘ status: 403    ∘contenttype: application/json    ∘ body: {“error”:“client_not_active”,“error_description”:“client is not       active”}   redirect_uriparameter present:    ∘ status: 400    ∘ contenttype: application/json   ∘ body:  {“error”:“input_error”,“error_description”:“redirect_uri not       allowed”}

The server to server call from a client to the authorization server 191to obtain an access token from an authorization code API URL displayedabove includes the contents of a sample JSON request and response. Asdisplayed, the request may include an URL parameters including theauthorization code provided in the call to /oauth2/authorize, the clientID requesting access to a user's data, the client secret key provided bythe authorization server 191 to the client, and the grant type. Theresponse may include a status, content type, and a body including fieldsrelated to the access token, and the expires in number of seconds untilthe token expires. An error may occur in several scenarios includingwhen a parameter is missing, an authorization code is not found, anauthorization code expired, a client secret not found, a client is notactive and a redirect URI parameter is present. If any of the aboveerrors occurs, an error response may include a status including adifferent status ID for the error, content type, and a body including amessage indicating which error occurred.

In some embodiments, an API URL to populate a target structure with afake device (e.g., thermostat, smoke detector) to test a client's accessand/or usage of the data model may be used. A response may include astatus and an empty message body for the sub-elements of the fakedevice.

In some embodiments, an API URL to delete a session (invalidate theaccess token) may be used. A request to delete the session, whichinvalidates the access token, may include the access token to beinvalidated. A response may include a status.

iii. Data Model

As discussed above, clients 182 communicate with the structures 10D anddevices (e.g. 10A-10C) via a shared data model (e.g., a shared JSONdocument) stored and/or accessible by the device service 84. Forexample, application programming interface (API) clients or API clientdevices may send one or more requests to the API 90 or device service 84to retrieve, access, view, subscribe, or modify data in the data modelrepresentative of one or more smart environments. Sending the requestsmay be implemented by the API client or API client device as computerinstructions stored on one or more tangible, non-transitorycomputer-readable media and executed by a processor. Data in the datamodel may be organized hierarchically. At the top level of the hierarchyare metadata, devices, and structures. Specific device types are modeledunder the devices object, such as thermostats and/or hazard detectors(e.g., smoke and CO alarms). In some embodiments, the metadata dataobject, the devices data object, and the structures data object may bepeers relative to one another (e.g., at the same relative level to oneanother) in the hierarchy. In addition, the data model may be a singleunified instance that is scalable for additional devices (e.g.,thermostats, hazard detectors, and/or party devices), companies, and/orstructures. For example, below is an example of a hierarchicallystructured data model, in accordance with an embodiment.

Data Model with Metadata, Devices, and Structures {  “metadata”: { “access_token”: “c.FmDPkzyzaQe...” ,  “client_version”: 1  }, “devices”: {  “thermostats”: {   “peyiJNo0IldT2YlIVtYaGQ”: {   “device_id”: “peyiJNo0IldT2YlIVtYaGQ” ,    “locale”: “en-US” ,   “software_version”: “4.0” ,    “structure_id”:“VqFabWH21nwVyd4RWgJgNb292wa7hG_dUwo2i2SG7j3- BOLY0BA4sw” ,    “name”:“Hallway (upstairs)” ,    “name_long”: “Hallway Thermostat (upstairs)” ,   “last_connection”: “2015-10-31T23:59:59.000Z” ,    “is_online”: true,    “can_cool”: true ,    “can_heat”: true ,   “is_using_emergency_heat”: true ,    “has_fan”: true ,   “fan_timer_active”: true ,    “fan_timer_timeout”:“2015-10-31T23:59:59.000Z” ,    “has_leaf”: true ,   “temperature_scale”: “C” ,    “target_temperature_f”: 72 ,   “target_temperature_c”: 21.5 ,    “target_temperature_high_f”: 72 ,   “target_temperature_high_c”: 21.5 ,    “target_temperature_low_f”: 64,    “target_temperature_low_c”: 17.5 ,    “away_temperature_high_f”: 72,    “away_temperature_high_c”: 21.5 ,    “away_temperature_low_f”: 64 ,   “away_temperature_low_c”: 17.5 ,    “hvac_mode”: “heat” ,   “ambient_temperature_f”: 72 ,    “ambient_temperature_c”: 21.5 ,   “humidity”: 40   }  },  “smoke_co_alarms”: {  “RTMTKxsQTCxzVcsySOHPxKoF4OyCifrs”: {    “device_id”:“RTMTKxsQTCxzVcsySOHPxKoF4OyCifrs” ,    “locale”: “en-US” ,   “software_version”: “1.01” ,    “structure_id”:“VqFabWH21nwVyd4RWgJgNb292wa7hG_dUwo2i2SG7j3- BOLY0BA4sw” ,    “name”:“Hallway (upstairs)” ,    “name_long”: “Hallway Protect (upstairs)” ,   “last_connection”: “2015-10-31T23:59:59.000Z” ,    “is_online”: true,    “battery_health”: “ok” ,    “co_alarm_state”: “ok” ,   “smoke_alarm_state”: “ok” ,    “is_manual_test_active”: true ,   “last_manual_test_time”: “2015-10-31T23:59:59.000Z” ,   “ui_color_state”: “gray”   }  },  “$company”: {   “$product_type”: {   “CPMEMSnC48JlSAHjQIp-aHI72IjLYHK_ul_c54UFb8CmPXNj4ixLbg”: {    “identification”: {      “device_id”: “CPMEMSnC48JlSAHjQIp-kHI72IjLYHK_ul_c54UFb8CmPXNj4ixLbg” ,      “serial_number”:“1L090B50230”     },     “location”: {      “structure_id”:“VqFabWH21nwVyd4RWgJgNb292wa7hG_dUwo2i2SG7j3- BOLY0BA4sw”     },    “software”: {      “version”: “1.0”     },     “resource_use”: {     “electricity”: {       “value”: 42.789 ,      “measurement_reset_time”: “2015-01-01T01:01:01.000Z” ,      “measurement_time”: “2015-01-01T01:02:35.000Z”      },      “gas”:{       “value”: 0.345234545 ,       “measurement_reset_time”:“2015-01-01T01:01:01.000Z” ,       “measurement_time”:“2015-01-01T01:02:35.000Z”      },      “water”: {       “value”:10000.3 ,       “measurement_reset_time”: “2015-01-01T01:01:01.000Z” ,      “measurement_time”: “2015-01-01T01:02:35.000Z”      }     }    }  }  }  },  “structures”: { “VqFabWH21nwVyd4RWgJgNb292wa7hG_dUwo2i2SG7j3-BOLY0BA4sw”: {  “structure_id”: “VqFabWH21nwVyd4RWgJgNb292wa7hG_dUwo2i2SG7j3-BOLY0BA4sw” ,   “thermostats”: [ “peyiJNo0IldT2YlIVtYaGQ”, ... ] ,  “smoke_co_alarms”: [ “RTMTKxsQTCxzVcsySOHPxKoF4OyCifrs”, ... ] ,  “devices”: {    “$company”: {     “$product_type”: [“CPMEMSnC48JlSAHjQIp- aHI72IjLYHK_ul_c54UFb8CmPXNj4ixLbg”, ... ]    }  },   “away”: “home” ,   “name”: “Home” ,   “country_code”: “US” ,  “postal_code”: “94304” ,   “peak_period_start_time”:“2015-10-31T23:59:59.000Z” ,   “peak_period_end_time”:“2015-10-31T23:59:59.000Z” ,   “time_zone”: “America/Los_Angeles” ,  “eta”: {    “trip_id”: “myTripHome1024” ,   “estimated_arrival_window_begin”: “2015-10-31T22:42:59.000Z” ,   “estimated_arrival_window_end”: “2015-10-31T23:59:59.000Z”   }  }  }}

As illustrated, metadata may be added to the data model. The metadataobject includes additional information that is provided when making acall to the API (e.g., via REST and/or Firebase). The access_tokenelement acts as an authorization element that is used to provide proofthat a user has authorized the client 182 to make API calls on theirbehalf. The access_token element is also used to identify which user towhich the data is associated with when receiving responses from a MUIcall, as described above. The client_version is an indication of thelast user-authorized version of a client 182 and is associated with theaccess_token.

Further, specific device types are modeled under the “devices” object.For example, in the current example, a thermostat 10A and detector 10Bare modeled. It should be noted that other devices types may be modeled,such as cameras, security alarms, and the like. Additionally, a“company” object may be modeled under the “devices” object, as explainedin detail below. Further, a structure is modeled. A structure representsa physical building. Structures 10D contain devices (e.g. 10A-10C) aswell as information for the building as a whole. For example, in oneembodiment, an estimated time of arrival to the structure 10D and/or an“away” mode indicating that no one is currently occupying the structuremay be maintained at the data model. Each of the devices and/orstructures has an associated unique identifier, which enables the APIcalls to be accurately routed to the proper device object.

In some embodiments, the data model may be hierarchically constructed ina manner where the structures are at a higher level and devices are at asub-level of a corresponding structure that the devices are associatedwith. Users of the system 180 may each have their own structure and/ordevice objects in the data model, which may be identified by anassociated user identifier. Below is an example of a data modelstructure, where structures and devices are associated with a user.

Example Data Model 1 {  “auth”: {   “505”: {    “myapp”: “antoken”//antoken is a customized token payload   }  },  “users”: {   “505”: {//505 is a unique user identifier    “structures”: { //structures object    “f3d0c560-03f2-11e1-98a4-1231381aa376”: { //structures     uniqueidentifier      “country_code”: “US”,      “name”: “home”,      “away”:false,      “location”: “Sunnyvale, CA”,      “postal_code”: “94087”,     “away_setter”: 1      “devices”: { // device associated with thestructure       “01AA01AB431100RF”: { //device unique identifier      “temperature_scale”: “F”,       “country_code”: “US”,      “current_temperature”: 21.5,       “name”: “Senior Zirconia”,      “fan_mode”: “auto”,       “device_locale”: “en_US”,      “target_temperature_type”: “heat”,       “can_cool”: false,      “postal_code”: “94087”,       “current_humidity”: 52,      “can_heat”: true,       “last_connection”: 1355181256000,      “has_fan”: false,       “target_temperature”: 20,       “online”:false       }      }     }   }  }  } }

As illustrated, in the above embodiment, structuref3d0c560-03f2-11e1-98a4-1231381aa376 is implemented as a sub-level ofthe user 505, indicating that the structure is associated with thisuser. Any number of structures may be implemented and/or associated witha particular user. Further, one structure may be associated with manyusers. Further, the device 01AA01AB431100RF is implemented as asub-level of structure object f3d0c560-03f2-11e1-98a4-1231381aa376,indicating that this device is a device of that structure. Any number ofdevices may be implemented and/or associated with a particularstructure.

In an alternative embodiment, a topology of associations between devicesand structures may be provided in the data model, as illustrated in thefollowing Example Data Model 2:

Example Data Model 2 { “users”: {  “505”: {   “structures”: {    “s1”: {},    “s2”: { }   }   “devices”: {    “d1”: { }    “d2”: { }   }  “topology”: {    “structures”: {     “s1”: [“d1”, “d2”],     “s2”:[“d3”]    },    “properties”: {    },    “wings”: {    },    “floors”: {   }   }  } }

In Example Data Model 2, two structures s1 and s2 are associated withuser 505. Further, devices d1 and d2 are associated with the user 505.The topology section associates the devices d1 and d2 with the structures1 and associates a third device d3 that is not associated with the user505 to the structure s2.

Honing in on the device objects, the devices (e.g., 10A-10C) may share acommon base set of information such as a user-supplied name, softwareversion and online status. Additionally, the data model may includeinformation specific to a particular device type. For example, smokeand/or CO detectors 10B may build upon the common base set ofinformation, adding alarm states. Further, thermostats 10A may add uponthe common base set of information to add data that may enable controlof HVAC systems and data regarding an observed climate of thermostat10A. Below is an example of thermostat 10A and detector 10B objects ofthe data model.

Devices Data Model Objects {  “devices”: {    “thermostats”: {    “peyiJNo0IldT2YlIVtYaGQ”: {       “device_id”:“peyiJNo0IldT2YlIVtYaGQ” ,       “locale”: “en-US” ,      “software_version”: “4.0” ,       “structure_id”:“VqFabWH21nwVyd4RWgJgNb292wa7hG_dUwo2i2SG7j3-BOLY0BA4sw” ,       “name”:“Hallway (upstairs)” ,       “name_long”: “Hallway Thermostat(upstairs)” ,       “last_connection”: “2014-10-31T23:59:59.000Z” ,      “is_online”: true ,       “can_cool”: true ,       “can_heat”:true ,       “is_using_emergency_heat”: true ,       “has_fan”: true ,      “fan_timer_active”: true ,       “fan_timer_timeout”:“2014-10-31T23:59:59.000Z” ,       “has_leaf”: true ,      “temperature_scale”: “C” ,       “target_temperature_f”: 72 ,      “target_temperature_c”: 21.5 ,       “target_temperature_high_f”:72 ,       “target_temperature_high_c”: 21.5 ,      “target_temperature_low_f”: 64 ,       “target_temperature_low_c”:17.5 ,       “away_temperature_high_f”: 72 ,      “away_temperature_high_c”: 21.5 ,       “away_temperature_low_f”:64 ,       “away_temperature_low_c”: 17.5 ,       “hvac_mode”: “heat” ,      “ambient_temperature_f”: 72 ,       “ambient_temperature_c”: 21.5,       “humidity”: 40     }    },    “smoke_co_alarms”: {    “RTMTKxsQTCxzVcsySOHPxKoF4OyCifrs”: {       “device_id”:“RTMTKxsQTCxzVcsySOHPxKoF4OyCifrs” ,       “locale”: “en-US” ,      “software_version”: “1.01” ,       “structure_id”:VqFabWH21nwVyd4RWgJgNb292wa7hG_dUwo2i2SG7j3-BOLY0BA4sw” ,       “name”:“Hallway (upstairs)” ,       “name_long”: “Hallway Protect (upstairs)” ,      “last_connection”: “2014-10-31T23:59:59.000Z” ,       “is_online”:true ,       “battery_health”: “ok” ,       “co_alarm_state”: “ok” ,      “smoke_alarm_state”: “ok” ,       “is_manual_test_active”: true ,      “last_manual_test_time”: “2014-10-31T23:59:59.000Z” ,      “ui_color_state”: “gray”     }    }    “$company”: {    “$product_type”: {    “CPMEMSnC48JlSAHjQIp-aHI72IjLYHK_ul_c54UFb8CmPXNj4ixLbg”: {      “identification”: {          “device_id”: “CPMEMSnC48JlSAHjQIp-kHI72IjLYHK_ul_c54UFb8CmPXNj4ixLbg” ,          “serial_number”:“1L090B50230”       },       “location”: {          “structure_id”:“VqFabWH21nwVyd4RWgJgNb292wa7hG_dUwo2i2SG7j3-BOLY0BA4sw”       },      “software”: {          “version”: “1.0”       },      “resource_use”: {        “electricity”: {          “value”: 42.789,          “measurement_reset_time”: “2015-01-01T01:01:01.000Z” ,         “measurement_time”: “2015-01-01T01:02:35.000Z”        },       “gas”: {          “value”: 0.345234545 ,         “measurement_reset_time”: “2015-01-01T01:01:01.000Z” ,         “measurement_time”: “2015-01-01T01:02:35.000Z”        },       “water”: {          “value”: 10000.3 ,         “measurement_reset_time”: “2015-01-01T01:01:01.000Z” ,         “measurement_time”: “2015-01-01T01:02:35.000Z”        }       }    }     }    }  } }

As illustrated, a device identifier (device_id:String) may be associatedwith the thermostat 10A and/or detector 10B. The device_id element holdsthe unique identifier of the particular device. Further, each device mayinclude the following elements: a country and language preference(locale:String), a software version (software_version: String), anassociated structure (structure_id:String), a name (name:String) (e.g.,short name for use in user interface labels), a long name(name_long:String) (e.g., for a more descriptive name), a lastconnection timestamp (last_connection:String), and a device connectionstatus (is_online:Boolean).

The thermostat may add additional elements. Some of the elements mayallow for the use of varied temperature scales (e.g., Fahrenheit and/orCelsius). The thermostat-specific elements may include: an indicationthat the HVAC system has a cooling ability (can_cool:Boolean), anindication that the HVAC system has a heating ability(can_heat:Boolean), a heat pump system emergency heating statusindicator (is_using_emergency_heat:Boolean), an indication of an abilityto control the fan separately from heating or cooling (has_fan:Boolean),an indication if the fan timer is engaged, which may be used with a fantimer timeout to turn on the fan for a user-specified preset duration(fan_timer_active:Boolean), a timestamp showing when the fan timerreaches 0 (fan_timer_timeout:String), an indicator to display anenergy-saving temperature indication (has_leaf:Boolean), a temperaturescale to use (e.g., Celsius or Fahrenheit (temperature_scale:String), adesired target Fahrenheit temperature (target_temperature_f:int), adesired target Celsius temperature (target_temperature_c:float), amaximum target temperature in Fahrenheit(target_temperature_high_f:int), a maximum target temperature in Celsius(target_temperature_high_c:float), a minimum target temperature inFahrenheit (target_temperature_low_f:int), a minimum target temperaturein Celsius (target_temperature_low_c:float), a maximum away temperaturein Fahrenheit (away_temperature_high_f:int), a maximum away temperaturein Celsius (away_temperature_high_c:float), a minimum away temperaturein Fahrenheit (away_temperature_low_f:int), a minimum away temperaturein Celsius (away_temperature_low_c:float), an HVAC mode indicatingheating, cooling, and/or heating-cooling modes (hvac_mode:String), anambient temperature measured at the thermostat 10A in whole degreesFahrenheit (ambient_temperature_f:float), an ambient temperaturemeasured at the thermostat 10A in half degrees Celsius(away_temperature_low_c:float).

The detectors 10B may include additional elements as well. Theseadditional elements may include: an indication of battery life/healthand/or an estimate of time to end of life of the detector 10B(battery_health:enum string), a carbon monoxide detection alarm state(co_alarm_state:enum string), a smoke detection alarm state(smoke_alarm_state:enum string), an indication of whether or not themanual smoke and carbon monoxide alarm test is active(is_manual_test_active:Boolean), a timestamp indicating the time of thelast successful manual test (last_manual_test_time:string), and/or anindicator of a color representative of device status (e.g., gray foroffline, green for OK, yellow for warning, and/or red for emergency)(ui_color_state:enum string). The indicator of the color representativeof device status may be derived from: is_online, battery_health,co_alarm_state, and/or smoke_alarm_state.

The company ($company:string) may represent a variable provided when aclient is created and provided the “product data read/write” scope. Thecompany variable may identify the company (e.g., client) as an entitythat can share product data with the API 90 and/or device service 84. Asillustrated, the company variable may include an element for a producttype variable ($product_type:string) that is provided when a client iscreated with the product data read/write” scope. The product typevariable may define the type of product, device, or appliancemanufactured by the company.

The product type variable may be an object or an array, depending on thestorage location. The product type variable may include a product uniqueidentifier. For each product unique identifier, there may be severaladditional elements. For example, each product unique identifier mayinclude an element for: identification, location, software, and resourceuse (resource_use). The identification (identification) element maycontain product identifiers. For example, the identification element maycontain: a device identifier (device_id:string), which is a uniquedevice identifier for the product; and a serial number(serial_number:string), which is a serial number of the product ordevice. The location element may include a unique identifier for thestructure (structure_id:string). The software element may include thesoftware version identifier for the product (version:string). Theresource use element may include elements for electricity, gas, and/orwater. The electricity, gas, and/or water elements may include resourceuse data values and measurement timestamps. For example, the environmentand gas elements may include a number of joules (value:number) consumedin a time period, a timestamp that identifies the start of themeasurement time period (measurement_reset_time:string), a timestampthat identifies the measurement_time (the time hwen the resource usedata was measured) (measurement_time:string). The water element mayinclude a number of liters consumed in the time period, a timestamp thatidentifies the start of the measurement time period(measurement_reset_time:string), a timestamp that identifies themeasurement time (the time hwen the resource use data was measured)(measurement_time:string). It should be noted that, the devices objectmay be scalable to include one or more company objects and each of theone or more company objects may be scalable to include one or moreproduct (e.g., device) type objects.

Additionally, as mentioned above, structures may be represented as anobject of the data model. Below is an example of a shared structureobject and its associated data that may be read and/or written to.

Structures Data Model Object {  “structures”: {  “VqFabWH21nwVyd4RWgJgNb292wa7hG_dUwo2i2SG7j3-BOLY0BA4sw”: {   “structure_id”: “VqFabWH21nwVyd4RWgJgNb292wa7hG_dUwo2i2SG7j3-BOLY0BA4sw” ,    “thermostats”: [ “peyiJNo0IldT2YlIVtYaGQ”, ... ] ,   “smoke_co_alarms”: [ “RTMTKxsQTCxzVcsySOHPxKoF4OyCifrs”, ... ] ,   “away”: “home” ,    “name”: “Home” ,    “country_code”: “US” ,   “postal_code”: “94304” ,    “peak_period_start_time”:“2014-10-31T23:59:59.000Z” ,    “peak_period_end_time”:“2014-10-31T23:59:59.000Z” ,    “time_zone”: “America/Los_Angeles” ,   “eta”: {     “trip_id”: “myTripHome1024” ,    “estimated_arrival_window_begin”: “2014-10-31T22:42:59.000Z” ,    “estimated_arrival_window_end”: “2014-10-31T23:59:59.000Z”    }   } } }

The structures object may include: a unique identifier:(structure_id:string), one or more lists of devices associated with thestructure (e.g., an array of thermostats 10A (thermostats:array) and/oran array of detectors 10B (smoke_co_alarms:array) that contain theunique identifiers of the thermostats 10A and/or detectors 10B,respectively). Further, the structure may include one or moreindications of characteristics and/or statuses of the structure. Forexample, the structure object may include: an indication of thestructure state (e.g., “away” state when no occupants are in thestructure) (away:string), a name associated with the structure(name:string), a country_code associated with the structure(country_code:string), a postal code associated with the structure(postal_code:string), a start time for an energy event (e.g. Rush HourRewards by Nest®) (peak_period_start_time:string), an end time for anenergy event (e.g. Rush Hour Rewards by Nest®)(peak_period_end_time:string), a time zone associated with the structure(time_zone:string), estimated time of arrival to the structure (etaobject that includes: a unique identifier for the estimated time ofarrival instance (trip_id:string), a beginning time for an estimatedarrival window (estimated_arrival_window_begin:string), and/or an endingtime for an estimated arrival window(estimated_arrival_window_end:string). In instances where there is aparticular estimated time of arrival rather than a window of arrivaltime, the beginning and end times may be set equal to the particularestimated time of arrival.

In the API 90, the concept of “Home” or “Away” is a powerful aspect thatmay affect the behaviors of certain smart device (e.g. thermostat 10A,detector 10B, and/or device 10C) features. For example, many energysavings and/or convenience features may be implemented using the “Home”or “Away” concept. For example, when integrated with other devices inthe structure via the API 90, clients 182 can further manage usercomfort and safety. For example, clients can: turn off the lights whenthe home goes into Away, send a notification if the house is Away andthe garage door is open, play music when the house switches to Home,etc.

The indication of structure state (e.g. “away” mode) may include anindication for “home” when someone is occupying the structure, “away”when a user has explicitly set the structure to away, and/or “auto-away”when it has algorithmically been determined that no one is in thestructure.

Users have the ability to manually activate Home/Away via smart devicecontrols, web applications, etc., while the API 90 offers an additionalaccess point via the clients 182. The API 90 provides the ability todirectly set Home and Away, as well as listen for changes to thesestates. Further, a variety of signals within the structure may be usedto detect human presence in a Home, and can set a sub-state of Away,called Auto-Away. If the device service 84 and/or the smart devicesdetect no presence for an extended period of time, they mayautomatically set the home to Auto-Away. Upon detection of humanpresence, the state of the structure may return to the Home state.

As mentioned above, depending on their access rights, clients 182 canread and/or write to the sections of the data model. Accordingly,subscribing to changes to the data model enables clients 182 to react inreal time to changes made to the system 180. Thus, using the API 90,clients 182 may access smart device services 84 to control and/orprovide data to one or more smart devices. For example, when a structureand/or thermostat is set to “away” mode, this status may be providedthrough the API 90 to the clients 182, which may then turn off one ormore devices (e.g., smart lighting systems, etc.).

In some embodiments, the device service 84 responds with a data objectincluding data objects from the data model (e.g., a metadata dataobject, a devices data object, a structures data object) based on therequest and scopes associated with the access token. Further, in someembodiments the clients 182 may perform a function in addition todisplaying the returned data in a page, such as controlling a setting onthe API client device based on the data, executing a control action onthe API client device based on the data, and the like.

iv. Third-Party Device Data Provisioning and Access

As previously discussed, vendors that do not have direct access to thedevice services 84 may wish to provide data to the device services 84for many reasons. For example, vendor data may be useful for reportingby the device services 84 and/or may be used in conditional triggers tocontrol one or more smart devices (e.g., thermostat 10A, detector 10B,and/or device 10C) and/or structures 10D that are under the influence ofthe device service 84. Further, this data may be accessible by othervendors, who may base control of these or other smart devices based inpart upon the provided vendor data.

Further, the device service 84 provider may desire to expand a sensornetwork within the structure 10D and/or improve device (e.g., 10A-10C)and/or structure 10D reporting and/or control algorithms. Thus, it maybe beneficial to take in such data from third-parties (e.g., those whodo not have direct access to the device services 84). Accordingly, theAPI 90 may include support for data provision from these third-parties.

Specifically, the APIs 90 may support the reception of data streams of“events” and/or “time variant data.” In one embodiment, the event datamay be provided as a named value with a name, timestamp and other datathat may be extensible. Event data may be provided upon occurrence of aparticular event. For example, event data representative of motiondetection may occur when one or more third-party sensors detect motionin the structure 10D.

Time variant data provision may relate to providing an account of dataover varying time periods. For example, this data may provide ahistorical account of particular data values of a third-party sensor.Further details and examples of time variant profiles are described inU.S. Ser. No. 62/061,593, filed Oct. 8, 2014, entitled “Fabric Network,”which is incorporated by reference herein in its entirety for allpurposes. In some embodiments this may be supplemented with the currentdata values. For example, re-using the motion detection examplediscussed above, the time variant data provision may provide ahistorical account of motion detected by the third party sensor (e.g.,motion detected at 5:00, no motion detected at 6:00, etc.).

FIG. 15 is a schematic diagram, illustrating a third-party vendor anddevice provisioning system 500 that enables consumption of third-partydevice data via the API 90, in accordance with an embodiment. FIG. 16 isa flowchart, illustrating a process 600 for provisioning third-partyvendors and third-party devices, such that third-party device data maybe consumed via the API 90. FIG. 17 is a relational diagram,illustrating a relationship of entities stored in the system 500 whenprovisioning third-parties/third-party devices 502 in the system 500.For clarity, these FIGS. will be discussed together.

To consume data from a third-party and/or third-party device 502 (e.g.,via data sent through a third-party cloud 504 to the API 90), the system500 may be provided awareness information regarding the third-party(e.g., the “vendor”) and/or the third-party devices. This informationmay be stored in the system 500, in a manner that enables the system 500to identify and/or classify third-party data that is received. Thisawareness data (e.g., provisioning data) may be provided, for example,from the third-party and/or third-party device 904 and/or the API 90provider 506. This provisioning data may be provided to the Services191, which may include one or more provisioning modules (e.g., portionsof machine-readable instructions, implemented on a processor) forprovisioning a vendor (block 602) and/or for provisioning a device(block 604).

Vendor Provisioning

Vendors that wish to provide and/or retrieve data to and/or from thesystem 500 may be provisioned for such data provision and/or retrieval.By utilizing vendor provisioning, administrators of the system 500 maycontrol particular vendors that may interact with the system 500. Forexample, a vendor may provide a request for interactivity rights withthe system 500, which may be sent to the administrators of the system500. Once the administrators verify that the vendor is legitimate and/ormeets interactivity rights eligibility, the administrator may enable thevendor to provide vendor-specific information that may be used tofacilitate interactivity with the system 500.

Vendor provisioning (block 602) may begin by submitting, via aprovisioning process initiated by the third-party and/or third-partydevice 502 (e.g., via the third-party cloud 504) and/or by the APIprovider 506. In the provisioning process, the third-party and/orthird-party device 502 and/or by the API provider 506 may provide (e.g.,via a web service call) information to populate vendor-specificinformation (e.g., the vendor entity 702 of FIG. 17, which will bediscussed in more detail below) to the services 191. The services 191may maintain this vendor-specific information, which may be used to tieparticular devices with the newly provisioned vendor. Thus, if a requestfor device provisioning (block 604, which will be described in moredetail below) for “Device A” is provided by “Company B,” portions of thevendor-specific device information for “Company B” may be tied to devicetype-specific information for “Device A.” For example, as illustrated inFIG. 17, the Device Type Entity 704 has a “Produced By” relationshipwith the Vendor Entity 702.

Device Provisioning

To consume data from third-parties and/or third-party devices 502. Thesystem 500 may be provided particular information regarding the devices502. Specifically, a device manifest (e.g., the device manifest sectionillustrated in the Device Type Entity 704 of FIG. 17) is used tomaintain compatibility information regarding the third-party devices502. Information for the manifest may be provided via the third-partyand/or third-party device 502, a third-party cloud 504, and/or the APIprovider 506 to the services 191. The services 191 may consume thisinformation and create a device type definition for the device 502 beingprovisioned.

First, build-time profiles for expected third-party device types aredefined. These build-time profiles provide a description of particulardevice capabilities and/or metadata regarding data provided by thesedevices. For example, profiles may provide data type information, dataunits, data constraints, etc. These profiles may closely resemble Weaveprofiles, which are described in more detail in U.S. patent applicationSer. No. 13/926,335, filed Jun. 25, 2013, entitled “EfficientCommunication for Devices of a Home Network”, which is incorporated byreference in its entirety for all purposes. Weave is anapplication-layer protocol for communicating data. The profiles aredefined as protobuf messages using field metadata annotations todescribe manifest sections corresponding to a given profile and how thefragment of the data model JSON corresponding to a profile is validated.

Below is a code snippet example of the profile defining protobufdefinitions, in accordance with an embodiment.

Once the profiles are defined, these profiles may be imported and usedin subsequent device type manifests, which may be used to describeand/or translate received third-party device 502 data. In embodimentswhere a profile is compatible with Weave (or other application-layerprotocol), an indicator of this compatibility may be provided in theprofile (e.g., by providing the compatible Weave (or otherapplication-layer protocol) profile identifier in the profile). Uponrelease of the profiles, new device type manifests may be created usingthe released profiles. The device type manifests are runtime artifactsrepresented by a serialized protocol message and provide device typedefinitions for the particular third-party device 502 being provisioned.

Below is an example of a third-party device manifest. In particular, theexample third-party device manifest is for an Acme brand washer withrevision 201410161.0b that provides energy and water resource usage inthe supplied units. The device manifest enables the system 500 tounderstand data that is provided to it via this type of third-partydevice 502.

identification: < vendor_description: “Acme”, product_description:“WSHR1138”, revision: “201410161.0b”, >, resource_use: < electricty: <measure_type: ENERGY units: < units: < base: KILOGRAM > units: < base:METER exponent: 2 > units: < base: SECOND exponent: 2 > > description:“Energy consumption in joules” source: “power sensor” > water: <measure_type: VOLUME units: < units: < base: METER exponent: 3 >exponent: 3 > description: “Water consumption in liters” source:“Flowmeter” > >

These device type definitions may be provided to the device service 84,the applications 182 and/or 510, and/or the data warehouse 185, wherethey may be used to interpret and/or translate data received from thethird-party devices 502, as will be discussed in more detail below.

Device Pairing

Once the device type is defined, a device 502 of that type may be paired(block 606). Pairing of third-party devices 502 is essentiallyregistering the device 502 with the system 500, which may aid in thesystem 500's understanding of data provided by the device 502.

The pairing process includes two basic steps. In one step, the pairingprocess collects information about the device 502, such as a location(e.g., structure) of the device, a serial number (or other uniqueidentifier) of the device 502, etc. This information may be provided bya user attempting to pair the device 502 (e.g., via a graphical userinterface prompt requesting the device-specific information). Forexample, a pairing request (e.g., a REST message) may be provided to theAPI 90 from the third-party and/or third-party device 502 and/or thethird-party cloud 504. This pairing request may include thedevice-specific information. The API 90 may transform payload dataprovided in the pairing request into a format interpretable by theservices 191 and may provide the transformed data to the services 191.For example, the API 90 may receive the request in an ISO 8601 formatand translate data from the request into an alternative format expectedby the services 191.

In a second step, the pairing process determines the device type of thedevice 502 and ties the device type to the device-specific payload dataof the third-party device 502. To do this, the services 191 may retrievean associated provisioned device type and form a relationship betweenthe device-specific payload data and the associated device type. Forexample, as illustrated in FIG. 17, during the pairing process, theDevice Type entity 704 may be tied to the Device entity 706 (e.g., a“Has Type” relationship). Further, the Device entity 706 may be tied toa particular structure (e.g., an “Is Part Of” relationship).Additionally, historical device pairing information may be stored (e.g.,by the Device History entity 712).

Upon registration with the system 500, paired devices are then providedfor subsequent distribution by the publication service 508 (e.g., via anupdate message), which may lead to publication to the data warehouse 185(e.g., via a second update message).

Providing Device Data

Once the vendor is provisioned (block 602), the device is provisioned(block 604), and the device is paired (block 606), the system 500 isable to receive and interpret third-party and/or third party device 502data. The third-party and/or third party device 502 and/or thethird-party cloud 504 may provide data via a data provision message(e.g., a Firebase and/or REST message) to the API 90.

Upon receiving third-party data, the API 90 may translate the payloadinto a format interpretable by the device service 84. Upon receiving thetranslated payload, the device service 84 may retrieve the device typedefinition for the particular device 502. For example, when the deviceservice 84 starts, it may load all available device type definitionsfrom the services 191. If the device 502 is of a known device type(e.g., has an associated device type definition loaded in the deviceservice 84), the associated device type definition may be used tosubsequently translate and/or describe incoming data from the device 502and/or cloud 504. Occasionally, the device 502 may be of an unknowndevice type (e.g., has no associated device type definition loaded inthe device service 84). For example, a device type may be provisionedafter the device service loads all available device type definitions.When the device type is unknown (e.g., has no associated device typedefinition loaded in the device service 84), the device service 84 mayprovide a request to the services 191 for a new device type definitionassociated with the device 502. Upon receiving this new device typedefinition from the services 191, the new device type definition may beused to translate and/or describe incoming data from the device 502and/or cloud 504. This device type definition acquisition may occurduring pairing of the third-party device 502 and/or as data is receivedfrom the third-party device 502 and/or cloud 504

For example, the associated device type definition may be used todescribe incoming data from the third-party device 502 and/orthird-party cloud 504. The device service 84 may propogate third-partypayload data to the applications 182 and/or 510 and/or the publicationservice 508 (e.g., via a data update message), which may result in thepayload data being stored in the data warehouse 185 (e.g., via a secondupdate message). The device type definitions may be provided not only tothe device service 84, but also the applications 182 and/or 510, and/orthe data warehouse 185, which may enable the payload to be interpretedby each of these entities. For example, accumulated third-party payloaddata that is stored in the data warehouse 185 may be interpreted usingthe device type definition, such that an energy report 514 may beprovided to the user 512. Further, any other processing logic 516 mayuse the device type definition to understand the third-party payloaddata.

Below is an example of a sample third-party device data that conforms tothe device manifest example that is provided above. Specifically, thethird-party device data represents washer data that provides energy andwater usage. As illustrated below, the payload provides time-variantdata related to a particular instance (or instances of use) for thewasher with serial number 123456789.

{ “identification”: { “serial_number”: “123456789” }, “resource_use”: {“energy”: { “value”: 50.2, “measurement_reset_time”: 946684800,“measurement_time”: 1414794859  }, “water”: { “value”: 123.7,“measurement_reset_time”: 946684800, “measurement_time”: 1414794859  } }}

Data Entities

Moving now to a more-detailed discussion of data entities useful forthird-party data submission, FIG. 17 is a relationship diagram 700,illustrating the relationship between third-party vendor and/or deviceentities stored in the system 500 to enable third-party data consumptionand/or provision. Specifically, the vendor entity 702 represents athird-party entity that sends third-party device data. In someembodiments, access scopes may be based upon a vendor identity. Forexample, a vendor scope may correspond to an ability to read and writedata under a vendor path in the data model. Multiple clients 184 may beassociated with one vendor (e.g. third-party 502). The clients 184 maybe associated with a vendor entity 702. Accordingly, exchanging anaccess token granted to a client 184 associated to a vender entity 702(e.g., either directly or via a developer) may return permissionscorresponding to that vendor entity 702. The vendor entity 702 mayinclude a vendor path attribute, which may be unique across all vendorentities 702.

The 3P (third-party) Device type entity 704 represents a class ofdevices belonging to a single vendor that have the same informationpayload. Device types are immutable. Accordingly, once the device typemetadata is obtained, it can be cached indefinitely. Device types can beversioned. For example, differing data pathways may be provided fordevice types with different version. Thus, in one embodiment, versioningmay be handled, for example, by appending a version to common prefix,for example washer_v1 may relate to a first version of a dishwasherdevice type and washer_v2 may relate to a second version the dishwasherdevice type.

Using the vendor entity 702 and the 3P device type entity 704, thirdparty devices may be provisioned (block 604). The 3P device type entity704 includes a vendor identity attribute that identifies the vendor thatthe 3P device type entity 704 belongs to.

The 3P device type entity 704 includes a path attribute that may be usedto access devices of a particular device type. The path attribute may beunique across all device types for a particular vendor entity 702.Accordingly, device types may be retrieved using a combination of thevendor 702 path with the 3P device type 704 path.

Further, the device type entity 704 contains a serialized devicemanifest field that describes device metadata and payload for theparticular device type represented by the 3P device type entity 704.

The 3P (third-party) device entities 706 are created upon a firstpairing of the device 502 (block 606) with the API 90 and/or deviceservice 84. The device entity 706 represents an identifiable entity(e.g., a device) that produces data conforming to a given device type.For example, the device entity 706 might represent a particulardishwasher that conforms to the washer_v2 device type.

As discussed above, devices are associated with particular structureentities 708. The device entity 706 is paired with the structureentities 708, which is associated with a user entity 710. Further, adevice history entity 712 (e.g., a data table) stores a history ofpairings between the device entity 706 and the structure entity 708.

Pairing of the third-party device 502 may be triggered by providing aPOST request to the API 90 at the path/devices/<vendor_path>/<device_type_path> with a post body containingthe third-party device payload. Below is an example of such a post body.

POST request Body for Device Pairing { “identification”: {“serial_number”: “abcdefgh”, ... }, “location”: { “structure_id”:“VqFabWH21nwVyd4RWgJgNb292wa7hG_dUwo2i2SG7j3BOLY0BA4sw”, ... }, ... //other profiles }

As illustrated, the payload provided in the post body may includedevice-identifying information, such as a serial number (e.g.,identification/serial_number) and/or a structure identifier (e.g.,location/structure_id) of the structure associated with the device. Thedevice-identifying information may be used to uniquely identify a deviceof a particular type for a particular vendor, while the structureidentifier may indicate which structure the device should be paired to.In some embodiments, these fields may be required in order tosuccessfully pair with the API 90 and/or device service 84.

In the device services 84, each of the paired third-party devices 502may be stored in a “Third-Party Device” portion of the data model (e.g.,a specially designated portion of the data model for third-party devices502). These devices 502 may be provisioned at runtime, thus enablingintroduction of new third-party device pairings without requiring newservice stack releases.

When pairing completes successfully, the services 191 may provide anewly-assigned internal identifier for this third-party device 502. Thedevice service 84 may then insert this internal identifier into theoriginal payload (e.g., the POST request body) and return the result.Below is an example of the payload with added internal identifier.

Returned Payload after Pairing { “identification”: { “device_id”:“peyiJNo0IldT2YlIVtYaGQ”, “serial_number”: “abcdefgh”, ... },“location”: { “structure_id”:“VqFabWH21nwVyd4RWgJgNb292wa7hG_dUwo2i2SG7j3BOLY0BA4sw”, ... }, ... //other profiles }

Accordingly, the system 500 may now use and/or store device informationfrom the third-party devices 502. Thus, device data may then be providedto the device services (block 608) from these devices 502. Further, uponproper validation of a third-party and/or third-party device 502, athird-party application 182 and/or an application 510 of the APIprovider 506 may be used to provide this data to a user 512.

When devices 502 are no longer in use (or data is no longer provided tothe system 500), they may be unpaired from the system 500. To do this, aDELETE request to the API 90 at the path/devices/<vendor>/<device_type>/<device_id>. In some embodiments, theinternal device identifier is obfuscated during the pairing process. Insuch embodiments, the path point <device_id> may refer to the obfuscateddevice identifier. Based upon this DELETE request, the API 90 mayrequest the services 191 to delete the identified device 502. When theservices 191 complete the unpairing successfully, the services 191return a success indication to the API 90, which returns a similarindication.

The discussion now turns to a more detailed look at how the system 500consumes and/or presents third-party data. As mentioned above, accesspermissions to read and/or write to the data model may be defined usinga path leading to devices and/or structures. To enable definition ofpermissions for specific vendors, the path may include an intermediatereference to the particular vendor. For example, the devices attributemay include a sub-attribute named “vendor” or “vendor_path” followed bythe third-party vendor devices. Accordingly, the path to the third-partyvendor devices may include a vendor field, allowing particularpermissions to be provided for a particular third-party vendor.

The API 90 may receive a request to read and/or write data to the datamodel of the device service 84 and may then request authenticationrights (e.g., from the services 191). Upon verifying the authenticationrights, the API 90 may provide the vendor, device type, and/or deviceidentifier path elements to construct a corresponding device service 84read and/or write request that it provides to the device service 84.

The device service 84 may validate the received request. Uponvalidation, the request may be processed, resulting in the read and/orwrite to the data model.

v. Third-Party Insight Data Provision and Access

In some embodiments, a third-party vendor may desire to provideadditional data to the system 500. For example, the vendor may wish toprovide a stream of data relating to particular logs and/or metrics. Todo this, the third-party may provide a stream descriptor, whichdescribes the particular data that will be provided to the system 500.Then, the vendor may provide data in a format corresponding to thestream descriptor, noting the association with the stream descriptor.

Discussing first the stream descriptors, the stream descriptors providea description of any stream data that a third-party wishes to post.Below is an example of stream descriptor for amp and watt measurementsthat may be provided via a subsequent data stream.

Metric Stream Descriptor { “metric_stream_descriptor”: { “version”: 1 //version number “description”: “energy measurements”, // a human readabledescription of the stream “fields”: [ // a list of fields in a stream {“description”: “current”, // a human readable description of the field“relative”: true, // whether measurements are absolute or relative tothe preceding sample “exponent”: 1, // scaling (in base 10) for themeasurement “logical_minimum”: 0, // expected minimum for any sample.Need details on diff between this and physical “logical_maximum”: 100,// expected maximum for any sample. “physical_minimum”: 0,“physical_maximum”: 1000, “units”: { // an object describing the unitsfor samples in this field “system”: “si”, // this or english“description”: “Amps”, // human readable description “unit_composition”:[ {“quantity”: “current”, “exponent”: 1 } ] } }, { “description”:“Watts”, “relative”: true, “exponent”: 1, “logical_minum”: 0,“logical_maximum”: 100, “physical_minimum”: 0, “physical_maximum”: 1000,“units”: { “system”: “si”, “description”: “watts”, “unit_composition”: [// a more complicated example representing kg * m{circumflex over( )}2/s{circumflex over ( )}3 {“quantity”: “mass”, “exponent”: 1 },{“quantity”: “length”, “exponent”: 2 }, (“quantity”: “time”, “exponent”:−3 } ] } } ] } }

Additionally, state information regarding a device may be described andprovided by a third-party vendor. Below is a state-based streamdescriptor.

{ “state_stream_descriptor”: ( “version”: 1 // currently this shouldalways be 1 “description”: “smoke detector states”, // a human readabledescription of the stream “fields”: [ // a list of fields in a stream {“description”: “smoke”, // a human readable description of the field“states”: [ { “name”: “all clear”, “description”: “state when acceptablelevels of smoke are detected” “value”: 0 }, { “name”: “heads up 1”,“description”: “first gentle alert on smoke” “value”: 1 }, { “name”:“heads up 2”, “description”: “more urgent alert” “value”: 2 }, { “name”:“heads up 3”, “description”: “” “value”: 2 } }, { “description”: “co”,// a human readable description of the field “states”: [ { “name”: “allclear”, “description”: “state when acceptable levels of coare detected”“value”: 0 }, { “name”: “heads up 1”, “description”: “first gentle alerton co” “value”: 1 }, { “name”: “heads up 2”, “description”: “more urgentalert” “value”: 2 }, { “name”: “heads up 3”, “description”: “” “value”:2 } } ] } }

In creating the descriptors, the vendor may determine and indicatewhether the descriptor is for public or private use. Public descriptorscan be used by other developers, while private descriptors may only beused by the creating vendor. Accordingly, when the API 90 providerdesires, it can create public descriptors for third-party vendors touse, especially when the API 90 provider has particular information itwould like to collect from third-parties (e.g., energy usage, motionevents, carbon-monoxide states, etc.).

Upon completion of the creation of the stream descriptors, thedevelopers may provide the descriptor to the API 90, which may return adescriptor identifier. To post data, the third-party vendor may providethe data-stream in accordance with the format provided in thedescriptor, along with the descriptor identity provided from the API 90.Below is an example of data posted via a described data stream.

{ “stream”: { “descriptor”: { “developer”: 1240985, “id”: 1240958 }“source”: { “manufacturer”: “Nest”, “type”: “D2A”, “id”: 1240958098,“qualifier”: “the thermostat” } “data”: [ [12098650986098, 5.60986,1.23498], [12098650986099, 5.60986, 1.23498], [12098650986100, 5.60986,1.23498], [12098650986101, 5.60986, 1.23498], [12098650986102, 5.60986,1.23498], [12098650986103, 5.60986, 1.23498], [12098650986104, 5.60986,1.23498], [12098650986105, 5.60986, 1.23498] ] } }vi. Third-Party Activity Monitoring

As more third-parties utilize the API 90 to communicate with and/orcontrol the system 180, it may become increasingly beneficial to monitorthird-party activities.

Tracking API 90 activities may be desirable to determine a particularresponsible party for data reads and/or writes of the device service 84data model. The API 90 activity log may transparently capture both readand/or write operations that propagate from the API 90 on behalf of theclients 182 and/or the client 182 vendors.

Multiple levels of granularity may be used to track these data readsand/or writes. For example, activity logging logic (e.g., machineinstructions implemented on a processor-based computer system) may trackmodifications and/or access to the data model at the devices level, thestructure level, and/or an overall shared data level.

Below is an example of a JSON structure for an activity log. In someembodiments, the activity log data is provided based upon a particularaccount (e.g., at an account and/or user level).

Activity Log JSON Example Top Level { “sessions” : [<SessionDetails>] }SessionDetails: { “client_id”: <number>, “session_id”: <string>,“events”: [<EventSpecification>] } EventSpecification: { “action”:“put”/“subscribe”, “action_targets”: [<ActionTarget>], “timestamp”:<number: timestamp in ms, when modification took place>, } ActionTarget{ “bucket_name”: <full bucket name>, “type”: “merge/overwrite” (putonly), “value”: <json values that were put>, (put only) “oldvalue”:<full object response json, pre-put> (put, overwrite only)“structure_name”: <name field out of containing structure bucket>,“structure_id”: <structure identifier>, “where_id”: string(device/shared only, both put/subscribe), “where_name”: <name from wherebucket matching where_id> (device/shared only, both put/subscribe),“label”: <string from shared bucket> (device/shared only, bothput/subscribe) }

In certain embodiments, the “sessions” element at the top level is anarray maintained in sorted order by timestamp. When data from theactivity log is to be read, the number of returned events may bereduced, by returning only events that have occurred within a certaintime period (e.g., the last 5, 7, 10, 15 days, etc.). In someembodiments, this time period may be configured using a parameter (e.g.,in the read call, etc.).

The “events” are an array of events (e.g., “put” and/or data “subscribe”events) that may be a combination of actions (e.g. “action_targets”) andthe time in which the actions happened. As illustrated in the exampleabove, much event metadata may be captured. For example, “bucket_name”may represent a particular location where the event occurred. “Type” mayrefer to a particular event type (e.g., merge and/or overwrite for “put”activities). “Value” may refer to a new value that has been written viaa “put” activity and “oldvalue” may refer to the data that existed priorto the “put”. Structure information corresponding to the activity mayalso be stored (e.g., the structure name and/or identifier. Further,“where” information that describes a more granular location within thestructure may be provided (e.g., a “where” identifiers and/or name).

The “SessionDetails” may include a client 182 identifier, a sessionidentifier, and the events performed during the session. Accordingly,the activity logging logic may be used to obtain a particular client(e.g. “client_id”) responsible for performing a particular action (e.g.,a put and/or subscribe event).

In one embodiment, activity logs may be used by the API 90 vendor todetermine when API 90 activities have caused changes to smart devices(e.g., thermostats 10A, detectors 10B, and/or other smart devices 10C).For example, when unexpected target temperature changes occur at athermostat 10A, the activity logs may be used to discern if athird-party is responsible for the change.

Further, in some embodiments, one or more third-party vendors may beprovided access to the activity logs. The activity logs may help thethird-party vendors to understand how their client applications areeffecting the environment 30. In some embodiments, the third-partyvendors may access activity log entries for actions and/or events causedby all vendors. In alternative embodiments, the third-party vendors mayhave access to only the actions and/or events caused by that particularthird-party vendor.

The specific embodiments described above have been shown by way ofexample, and it should be understood that these embodiments may besusceptible to various modifications and alternative forms. It should befurther understood that the claims are not intended to be limited to theparticular forms disclosed, but rather to cover all modifications,equivalents, and alternatives falling within the spirit and scope ofthis disclosure.

1. One or more non-transitory, tangible, machine-readable mediacomprising instructions to: send one or more requests to retrieve,access, view, subscribe, or modify data in a data model representativeof one or more smart environments, wherein the data model comprises: ametadata object that includes an access token used to identify whichuser the data is associated with in the data model; a devices objectthat includes information related to one or more electronic devices; anda structures object that includes one or more references to the one ormore electronic devices in the one or more smart environments.
 2. Theone or more machine-readable media of claim 1, wherein the one or moreelectronic devices comprise: a thermostat; a hazard detector; a camera;a sensor of a security system; an electronic device produced by amanufacturer that does not host the data model in a service; or somecombination thereof.
 3. The one or more machine-readable media of claim1, wherein the metadata, the devices, and the structures objects arearranged in a hierarchical data structure in the data model.
 4. The oneor more machine-readable media of claim 3, wherein the metadata,devices, and structures objects are at the same relative level to oneanother in the hierarchical data structure of the data model.
 5. The oneor more machine-readable media of claim 1, comprising instructions toreceive one or more responses that include data elements in the metadataobject, the devices object, the structures object, or some combinationthereof based on the one or more requests.
 6. The one or moremachine-readable media of claim 1, wherein the devices object comprises:one or more thermostat objects that defines at least one or morethermostat temperature setpoints; one or more hazard detector objectsthat defines at least a state of a smoke alarm and a carbon monoxide(CO) alarm; and a company object that defines a company as an entitythat can share product data with a service, or some combination thereof;wherein the one or more thermostat objects, the one or more smoke and COalarm objects, and the company object are at the same relative level toone another in a hierarchical data structure of the data model.
 7. Theone or more machine-readable media of claim 6, wherein the datacomprises a target temperature setpoint included in the one or morethermostat objects of the data model.
 8. The one or moremachine-readable media of claim 6, wherein the data comprises an awaytemperature setpoint included in the one or more thermostat objects ofthe data model.
 9. The one or more machine-readable media of claim 6,wherein the data comprises a CO alarm state, a smoke alarm state, orboth, included in the one or more smoke and CO alarm objects of the datamodel.
 10. The one or more machine-readable media of claim 1, whereinthe data model is a single unified instance that scales to incorporateadditional electronic devices.
 11. An application programming interface(API) client device or API client comprising computer instructionsconfigured to: send one or more requests to retrieve, access, view,subscribe, or modify data in a data model representative of one or moresmart environments, wherein the data model comprises: a metadata objectthat includes an access token used to identify which user the datarepresents in the data model; a devices object that includes informationrelated to electronic devices; and a structures object that includes oneor more references to the electronic devices in the one or more smartenvironments.
 12. The API client device or API client of claim 11,wherein, based on the one or more requests, the devices object scales toinclude one or more company objects, and each of the one or more companyobjects scales to include one or more device type objects.
 13. The APIclient device or API client of claim 11, wherein the devices objectcomprises: one or more thermostat objects that defines at least one ormore thermostat temperature setpoints; one or more smoke and carbonmonoxide (CO) alarm objects that defines at least a state of smoke andCO alarms; and a company object that defines the third party as anentity that can share product data with a service, or some combinationthereof; wherein the one or more thermostat objects, the one or moresmoke and CO alarm objects, and the company object are at the samerelative level in the hierarchical data structure of the data model. 14.The API client device or API client of claim 13, wherein the one or morerequests are sent to an API interfacing with a service with directaccess to the data model.
 15. The API client device or API client ofclaim 11, wherein the data comprises: a data element included in thestructures object of the data model; wherein the data element isindicative of an estimated time of arrival of a person to the one ormore smart environments represented by the structures object.
 16. TheAPI client device or API client of claim 11, wherein the data comprises:a data element included in the structures object of the data model;wherein the data element is indicative of whether a user is away fromthe one or more smart environments represented by the structures object.17. A method comprising: sending, via an application programminginterface (API) client device or an API client, one or more requests toretrieve, access, view, subscribe, or modify data in a data modelrepresentative of one or more smart environments, wherein the data modelcomprises: a metadata object that includes an access token used toidentify which user the data represents in the data model; a devicesobject that includes information related to electronic devices; and astructures object that includes one or more references to the electronicdevices in the one or more smart environments.
 18. The method of claim17, comprising receiving, via the API client device or the API client,one or more responses that include data from the metadata object, thedevices object, the structures object, or some combination thereof basedon the one or more requests.
 19. The method of claim 18, comprisingperforming a function using the data, wherein the function comprisesdisplaying the data, controlling a setting on the API client devicebased on the data, executing a control action on the API client devicebased on the data, or some combination thereof.
 20. The method of claim17, wherein the one or more requests include information related to theAPI client device or the API client, wherein the information comprises:a company that manufactures the API client device; a device type of theAPI client device; one or more resources consumed by the API clientdevice; or some combination thereof.